From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org, shivani.agarwal@broadcom.com
Cc: Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH v5.10] block: don't call rq_qos_ops->done_bio if the bio isn't tracked
Date: Tue, 29 Jul 2025 15:37:34 -0400 [thread overview]
Message-ID: <1753812096-cfcbafef@stable.kernel.org> (raw)
In-Reply-To: <20250729050901.98518-1-shivani.agarwal@broadcom.com>
[ Sasha's backport helper bot ]
Hi,
Summary of potential issues:
⚠️ Found follow-up fixes in mainline
The upstream commit SHA1 provided is correct: a647a524a46736786c95cdb553a070322ca096e3
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)
Found fixes commits:
aa1b46dcdc7b block: fix rq-qos breakage from skipping rq_qos_done_bio()
Note: The patch differs from the upstream commit:
---
1: a647a524a467 < -: ------------ block: don't call rq_qos_ops->done_bio if the bio isn't tracked
-: ------------ > 1: 2b3b2e94a12e block: don't call rq_qos_ops->done_bio if the bio isn't tracked
---
Results of testing on various branches:
| Branch | Patch Apply | Build Test |
|---------------------------|-------------|------------|
| origin/linux-5.10.y | Success | Success |
prev parent reply other threads:[~2025-07-29 19:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-29 5:09 [PATCH v5.10] block: don't call rq_qos_ops->done_bio if the bio isn't tracked Shivani Agarwal
2025-07-29 19:37 ` 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=1753812096-cfcbafef@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.