From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: Harshit Mogalapalli <harshit.m.mogalapalli@oracle.com>,
Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH 6.1.y 2/2] exfat: fix potential deadlock on __exfat_get_dentry_set
Date: Sun, 15 Dec 2024 12:51:31 -0500 [thread overview]
Message-ID: <20241215092945-d5eebef117fc6a59@stable.kernel.org> (raw)
In-Reply-To: <20241214221839.3274375-2-harshit.m.mogalapalli@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: Harshit Mogalapalli <harshit.m.mogalapalli@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
Note: The patch differs from the upstream commit:
---
Failed to apply patch cleanly, falling back to interdiff...
interdiff error output:
/home/sasha/stable/mailbot.sh: line 525: interdiff: command not found
interdiff failed, falling back to standard diff...
---
Results of testing on various branches:
| Branch | Patch Apply | Build Test |
|---------------------------|-------------|------------|
| stable/linux-6.1.y | Success | Success |
next prev parent reply other threads:[~2024-12-15 17:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-14 22:18 [PATCH 6.1.y 1/2] exfat: support dynamic allocate bh for exfat_entry_set_cache Harshit Mogalapalli
2024-12-14 22:18 ` [PATCH 6.1.y 2/2] exfat: fix potential deadlock on __exfat_get_dentry_set Harshit Mogalapalli
2024-12-15 17:51 ` Sasha Levin [this message]
2024-12-15 17:51 ` [PATCH 6.1.y 1/2] exfat: support dynamic allocate bh for exfat_entry_set_cache Sasha Levin
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=20241215092945-d5eebef117fc6a59@stable.kernel.org \
--to=sashal@kernel.org \
--cc=harshit.m.mogalapalli@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 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.