From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: guocai.he.cn@windriver.com, Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH][5.15.y] gfs2: Fix slab-use-after-free in gfs2_qd_dealloc
Date: Wed, 11 Dec 2024 11:32:12 -0500 [thread overview]
Message-ID: <20241211092532-a65949c2ef78e550@stable.kernel.org> (raw)
In-Reply-To: <20241211075458.3346123-1-guocai.he.cn@windriver.com>
[ Sasha's backport helper bot ]
Hi,
The claimed upstream commit SHA1 (7ad4e0a4f61c57c3ca291ee010a9d677d0199fba) was not found.
However, I found a matching commit: bdcb8aa434c6d36b5c215d02a9ef07551be25a37
WARNING: Author mismatch between patch and found commit:
Backport author: guocai.he.cn@windriver.com
Commit author: Juntong Deng <juntong.deng@outlook.com>
Status in newer kernel trees:
6.12.y | Present (exact SHA1)
6.6.y | Present (different SHA1: 08a28272faa7)
6.1.y | Present (different SHA1: 7ad4e0a4f61c)
5.15.y | Not found
Note: The patch differs from the upstream commit:
---
1: bdcb8aa434c6d < -: ------------- gfs2: Fix slab-use-after-free in gfs2_qd_dealloc
-: ------------- > 1: 984007af06c33 gfs2: Fix slab-use-after-free in gfs2_qd_dealloc
---
Results of testing on various branches:
| Branch | Patch Apply | Build Test |
|---------------------------|-------------|------------|
| stable/linux-5.15.y | Success | Success |
next prev parent reply other threads:[~2024-12-11 16:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-11 7:54 [PATCH][5.15.y] gfs2: Fix slab-use-after-free in gfs2_qd_dealloc guocai.he.cn
2024-12-11 8:02 ` Greg KH
2024-12-11 16:32 ` Sasha Levin [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-12-11 8:39 guocai.he.cn
2024-12-11 16:33 ` Sasha Levin
2024-12-12 11:59 ` 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=20241211092532-a65949c2ef78e550@stable.kernel.org \
--to=sashal@kernel.org \
--cc=guocai.he.cn@windriver.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