From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org, songmuchun@bytedance.com
Cc: Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH 5.15.y] block: fix ordering between checking QUEUE_FLAG_QUIESCED request adding
Date: Mon, 17 Mar 2025 12:40:03 -0400 [thread overview]
Message-ID: <20250317085133-b618b4ac697a8a12@stable.kernel.org> (raw)
In-Reply-To: <20250317072021.22578-1-songmuchun@bytedance.com>
[ Sasha's backport helper bot ]
Hi,
Summary of potential issues:
⚠️ Found matching upstream commit but patch is missing proper reference to it
Found matching upstream commit: 6bda857bcbb86fb9d0e54fbef93a093d51172acc
Status in newer kernel trees:
6.13.y | Present (exact SHA1)
6.12.y | Present (different SHA1: 2094bd1b5225)
6.6.y | Present (different SHA1: 679b1874eba7)
6.1.y | Not found
Note: The patch differs from the upstream commit:
---
1: 6bda857bcbb86 < -: ------------- block: fix ordering between checking QUEUE_FLAG_QUIESCED request adding
-: ------------- > 1: e5851a818c868 block: fix ordering between checking QUEUE_FLAG_QUIESCED request adding
---
Results of testing on various branches:
| Branch | Patch Apply | Build Test |
|---------------------------|-------------|------------|
| stable/linux-5.15.y | Success | Success |
next prev parent reply other threads:[~2025-03-17 16:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-03 10:10 FAILED: patch "[PATCH] block: fix ordering between checking QUEUE_FLAG_QUIESCED" failed to apply to 5.15-stable tree gregkh
2025-03-17 3:29 ` [PATCH 5.15.y] block: fix ordering between checking QUEUE_FLAG_QUIESCED request adding Muchun Song
2025-03-17 6:56 ` Greg KH
2025-03-17 16:40 ` Sasha Levin
2025-03-17 7:20 ` Muchun Song
2025-03-17 16:40 ` Sasha Levin [this message]
2025-04-22 12:21 ` Greg KH
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=20250317085133-b618b4ac697a8a12@stable.kernel.org \
--to=sashal@kernel.org \
--cc=songmuchun@bytedance.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.