From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org, shivani.agarwal@broadcom.com
Cc: Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH 2/2 v5.10] dm rq: don't queue request to blk-mq during DM suspend
Date: Mon, 11 Aug 2025 18:30:30 -0400 [thread overview]
Message-ID: <1754925507-8563750b@stable.kernel.org> (raw)
In-Reply-To: <20250811052702.145189-3-shivani.agarwal@broadcom.com>
[ Sasha's backport helper bot ]
Hi,
Summary of potential issues:
❌ Build failures detected
The upstream commit SHA1 provided is correct: b4459b11e84092658fa195a2587aff3b9637f0e7
WARNING: Author mismatch between patch and upstream commit:
Backport author: Shivani Agarwal <shivani.agarwal@broadcom.com>
Commit author: Ming Lei <ming.lei@redhat.com>
Status in newer kernel trees:
6.15.y | Present (exact SHA1)
6.12.y | Present (exact SHA1)
6.6.y | Present (exact SHA1)
6.1.y | Present (exact SHA1)
5.15.y | Present (exact SHA1)
Note: The patch differs from the upstream commit:
---
1: b4459b11e840 ! 1: d0cf570e337e dm rq: don't queue request to blk-mq during DM suspend
@@ Metadata
## Commit message ##
dm rq: don't queue request to blk-mq during DM suspend
+ commit b4459b11e84092658fa195a2587aff3b9637f0e7 upstream.
+
DM uses blk-mq's quiesce/unquiesce to stop/start device mapper queue.
But blk-mq's unquiesce may come from outside events, such as elevator
@@ Commit message
Cc: stable@vger.kernel.org
Signed-off-by: Ming Lei <ming.lei@redhat.com>
Signed-off-by: Mike Snitzer <snitzer@redhat.com>
+ Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
+ [Shivani: Modified to apply on 5.10.y]
+ Signed-off-by: Shivani Agarwal <shivani.agarwal@broadcom.com>
## drivers/md/dm-rq.c ##
@@ drivers/md/dm-rq.c: static blk_status_t dm_mq_queue_rq(struct blk_mq_hw_ctx *hctx,
@@ drivers/md/dm-rq.c: static blk_status_t dm_mq_queue_rq(struct blk_mq_hw_ctx *hct
+
if (unlikely(!ti)) {
int srcu_idx;
- struct dm_table *map = dm_get_live_table(md, &srcu_idx);
+ struct dm_table *map;
---
Results of testing on various branches:
| Branch | Patch Apply | Build Test |
|---------------------------|-------------|------------|
| origin/linux-5.10.y | Success | Failed |
Build Errors:
origin/linux-5.10.y:
Build error: Building current HEAD with log output
Build x86: exited with code 2
Cleaning up worktrees...
Cleaning up worktrees...
Cleaning up worktrees...
Cleaning up worktrees...
prev parent reply other threads:[~2025-08-11 22:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-11 5:27 [PATCH 0/2 v5.10] Fix CVE-2021-47498 Shivani Agarwal
2025-08-11 5:27 ` [PATCH 1/2 v5.10] dm: rearrange core declarations for extended use from dm-zone.c Shivani Agarwal
2025-08-11 22:30 ` Sasha Levin
2025-08-11 5:27 ` [PATCH 2/2 v5.10] dm rq: don't queue request to blk-mq during DM suspend Shivani Agarwal
2025-08-11 22:30 ` Sasha Levin [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1754925507-8563750b@stable.kernel.org \
--to=sashal@kernel.org \
--cc=shivani.agarwal@broadcom.com \
--cc=stable@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox