From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: Xiangyu Chen <xiangyu.chen@eng.windriver.com>,
Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH RFC 5.15] smb: client: fix potential UAF in cifs_stats_proc_write()
Date: Thu, 13 Mar 2025 05:08:33 -0400 [thread overview]
Message-ID: <20250312232106-6b48ce51979f992a@stable.kernel.org> (raw)
In-Reply-To: <20250310014114.3430531-1-xiangyu.chen@eng.windriver.com>
[ Sasha's backport helper bot ]
Hi,
✅ All tests passed successfully. No issues detected.
No action required from the submitter.
The upstream commit SHA1 provided is correct: d3da25c5ac84430f89875ca7485a3828150a7e0a
WARNING: Author mismatch between patch and upstream commit:
Backport author: Xiangyu Chen<xiangyu.chen@eng.windriver.com>
Commit author: Paulo Alcantara<pc@manguebit.com>
Status in newer kernel trees:
6.13.y | Present (exact SHA1)
6.12.y | Present (exact SHA1)
6.6.y | Present (different SHA1: cf03020c56d3)
6.1.y | Present (different SHA1: 8fefd166fcb3)
Note: The patch differs from the upstream commit:
---
1: d3da25c5ac844 < -: ------------- smb: client: fix potential UAF in cifs_stats_proc_write()
-: ------------- > 1: b543f15d675d5 smb: client: fix potential UAF in cifs_stats_proc_write()
---
Results of testing on various branches:
| Branch | Patch Apply | Build Test |
|---------------------------|-------------|------------|
| stable/linux-5.15.y | Success | Success |
prev parent reply other threads:[~2025-03-13 9:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-10 1:41 [PATCH RFC 5.15] smb: client: fix potential UAF in cifs_stats_proc_write() Xiangyu Chen
2025-03-13 9:08 ` 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=20250312232106-6b48ce51979f992a@stable.kernel.org \
--to=sashal@kernel.org \
--cc=stable@vger.kernel.org \
--cc=xiangyu.chen@eng.windriver.com \
/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