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:

https://lore.kernel.org/linux-block/YRHyYmqxNSMMdyXo@T590/T/#t

block layer can't support mixed traditional discard range and
multi-range discard. But the issue existed since adding
multi-range discard.

The fix will land v5.15, so rhel9 needs to backport the fix


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

9.0

How reproducible:

not easy to reproduce


Steps to Reproduce:

N/A


Actual results:


Expected results:


Additional info:

Hello Changhui,

Any chance to review and ack this BZ if you are fine.

(In reply to Ming Lei from comment #4)
> Hello Changhui,
> 
> Any chance to review and ack this BZ if you are fine.

Hello,Ming

setting qa_ack +

there is no reproducer available here. you mentioned that this issue is not easy to reproduce. 
is it enough for QE to run sanity testing here?

Thanks

sanity test passed with 5.14.0-9.mr79_211021_1728.el9:
https://beaker.engineering.redhat.com/jobs/5923128
https://beaker.engineering.redhat.com/jobs/5926381
https://beaker.engineering.redhat.com/jobs/5923129

setting to verified:tested

regression test pass with  kernel-5.14.0-10.el9:
https://beaker.engineering.redhat.com/jobs/5950305

all patches are included to kernel tree,
move to verified

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 (new packages: kernel), 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-2022:3907