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.
Bug 1997338 - block: update to upstream v5.14
Summary: block: update to upstream v5.14
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: kernel
Version: 8.6
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Ming Lei
QA Contact: ChanghuiZhong
URL:
Whiteboard:
Depends On:
Blocks: 1990475 2033623 2034395 2034396
TreeView+ depends on / blocked
 
Reported: 2021-08-25 02:00 UTC by Ming Lei
Modified: 2022-09-01 13:22 UTC (History)
12 users (show)

Fixed In Version: kernel-4.18.0-350.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 2034395 2034396 (view as bug list)
Environment:
Last Closed: 2022-05-10 15:06:29 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Gitlab redhat/rhel/src/kernel rhel-8 merge_requests 1386 0 None None None 2021-10-29 09:46:40 UTC
Red Hat Issue Tracker RHELPLAN-94697 0 None None None 2021-08-25 02:02:50 UTC
Red Hat Product Errata RHSA-2022:1988 0 None None None 2022-05-10 15:07:18 UTC

Description Ming Lei 2021-08-25 02:00:37 UTC
Update block layer to upstream v5.14, so that we can support new feature, and
align with upstream.

Most changes are in bug fixes, bfq update, blkcg update, block core and
related block drivers(drivers/block).

Comment 1 Ming Lei 2021-08-25 02:04:03 UTC
Any dependency on block layer from drivers, dm, md and others, please feel free to add there, so
we can discuss/track related changes.

Comment 19 ChanghuiZhong 2021-11-26 02:59:09 UTC
Regression test passed with  kernel-4.18.0-350.el8:
https://beaker.engineering.redhat.com/jobs/6021444
https://beaker.engineering.redhat.com/jobs/6028704

patches has included to kernel tree,
move to verified

Comment 20 Ewan D. Milne 2021-12-19 12:08:49 UTC
Request zStream for single patch from this MR to fix bug 2033623 in 8.5.0:


commit c3c99902c7bcb77eb6f2bc2cab1432dc75a3aee6
Author: Ming Lei <ming.lei>
Date:   Mon Sep 27 22:18:04 2021 +0800

    blk-mq: avoid to iterate over stale request
    
    Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1997338
    
    commit 67f3b2f822b7e71cfc9b42dbd9f3144fa2933e0b
    Author: Ming Lei <ming.lei>
    Date:   Mon Sep 6 14:50:03 2021 +0800
    
        blk-mq: avoid to iterate over stale request
    
        blk-mq can't run allocating driver tag and updating ->rqs[tag]
        atomically, meantime blk-mq doesn't clear ->rqs[tag] after the driver
        tag is released.
    
        So there is chance to iterating over one stale request just after the
        tag is allocated and before updating ->rqs[tag].
    
        scsi_host_busy_iter() calls scsi_host_check_in_flight() to count scsi
        in-flight requests after scsi host is blocked, so no new scsi command can
        be marked as SCMD_STATE_INFLIGHT. However, driver tag allocation still can
        be run by blk-mq core. One request is marked as SCMD_STATE_INFLIGHT,
        but this request may have been kept in another slot of ->rqs[], meantime
        the slot can be allocated out but ->rqs[] isn't updated yet. Then this
        in-flight request is counted twice as SCMD_STATE_INFLIGHT. This way causes
        trouble in handling scsi error.
    
        Fixes the issue by not iterating over stale request.
    
        Cc: linux-scsi.org
        Cc: "Martin K. Petersen" <martin.petersen>
        Reported-by: luojiaxing <luojiaxing>
        Signed-off-by: Ming Lei <ming.lei>
        Link: https://lore.kernel.org/r/20210906065003.439019-1-ming.lei@redhat.com
        Signed-off-by: Jens Axboe <axboe>
    
    Signed-off-by: Ming Lei <ming.lei>

Comment 21 Ewan D. Milne 2021-12-19 12:17:43 UTC
Should also request zStream for 8.4.0 for EUS.

Comment 25 errata-xmlrpc 2022-05-10 15:06:29 UTC
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 (Important: kernel security, 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/RHSA-2022:1988


Note You need to log in before you can comment on or make changes to this bug.