RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
In older versions of lz4 (anything older than 1.8.2) bit errors can be introduced when compressing from fragmented source memory (i.e., a sequence of non-continguous memory extents).

Version-Release number of selected component (if applicable):
lz4-1.7.5-3

How reproducible:
Always

Steps to Reproduce:
1.
2.
3.

Actual results:
Ceph clusters crash

Expected results:
Ceph clusters should not crash

Additional info:
Upstream thread at https://github.com/ceph/ceph/pull/33584 discusses the issue in detail and also has a reproducer. Fix of this issue is available at https://github.com/lz4/lz4/commit/af127334670a5e7b710bbd6adb71aa7c3ef0cd72, but backporting it alone seems impossible so rebase seems the most feasible option.

Hello 

Sorry for missing out on getting the justification as requested in comment #2. I've set the priority of this bug based on priority with which customer opened the case with Red Hat. I see bug has already got all the acks for RHEL-7.9, so I am clearing the needinfo for now. Let me know if there is anything I need to provide here.

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (lz4 bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2020:3957