From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: Sherry Yang <sherry.yang@oracle.com>, Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH 5.15.y, 5.10.y] exfat: fix potential deadlock on __exfat_get_dentry_set
Date: Sat, 14 Dec 2024 09:26:28 -0500 [thread overview]
Message-ID: <20241214091651-0af6196918c18d20@stable.kernel.org> (raw)
In-Reply-To: <20241213235705.2201714-1-sherry.yang@oracle.com>
[ Sasha's backport helper bot ]
Hi,
The upstream commit SHA1 provided is correct: 89fc548767a2155231128cb98726d6d2ea1256c9
WARNING: Author mismatch between patch and upstream commit:
Backport author: Sherry Yang <sherry.yang@oracle.com>
Commit author: Sungjong Seo <sj1557.seo@samsung.com>
Status in newer kernel trees:
6.12.y | Present (exact SHA1)
6.6.y | Present (different SHA1: a7ac198f8dba)
6.1.y | Not found
5.15.y | Not found
Note: The patch differs from the upstream commit:
---
1: 89fc548767a2 < -: ------------ exfat: fix potential deadlock on __exfat_get_dentry_set
-: ------------ > 1: 9b4fc692990f exfat: fix potential deadlock on __exfat_get_dentry_set
---
Results of testing on various branches:
| Branch | Patch Apply | Build Test |
|---------------------------|-------------|------------|
| stable/linux-5.15.y | Success | Failed |
| stable/linux-5.10.y | Success | Failed |
Build Errors:
Build error for stable/linux-5.15.y:
Build error for stable/linux-5.10.y:
make: *** No rule to make target 'allmodconfig'. Stop.
make: *** No targets specified and no makefile found. Stop.
next prev parent reply other threads:[~2024-12-14 14:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-13 23:57 [PATCH 5.15.y, 5.10.y] exfat: fix potential deadlock on __exfat_get_dentry_set Sherry Yang
2024-12-14 14:26 ` Sasha Levin [this message]
2024-12-14 17:57 ` Sherry Yang
2024-12-14 18:06 ` Greg KH
2024-12-14 21:41 ` Harshit Mogalapalli
2024-12-14 21:50 ` 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=20241214091651-0af6196918c18d20@stable.kernel.org \
--to=sashal@kernel.org \
--cc=sherry.yang@oracle.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