From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: Cliff Liu <donghua.liu@windriver.com>, Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH 5.15.y] smb: client: fix potential UAF in is_valid_oplock_break()
Date: Tue, 15 Apr 2025 17:43:07 -0400 [thread overview]
Message-ID: <20250415112449-0d403bda217b21ea@stable.kernel.org> (raw)
In-Reply-To: <20250415020212.320762-1-donghua.liu@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: 69ccf040acddf33a3a85ec0f6b45ef84b0f7ec29
WARNING: Author mismatch between patch and upstream commit:
Backport author: Cliff Liu<donghua.liu@windriver.com>
Commit author: Paulo Alcantara<pc@manguebit.com>
Status in newer kernel trees:
6.14.y | Present (exact SHA1)
6.13.y | Present (exact SHA1)
6.12.y | Present (exact SHA1)
6.6.y | Present (different SHA1: 0a15ba88a32f)
6.1.y | Present (different SHA1: 494c91e1e941)
Note: The patch differs from the upstream commit:
---
1: 69ccf040acddf < -: ------------- smb: client: fix potential UAF in is_valid_oplock_break()
-: ------------- > 1: 9bdb460b7ab1a smb: client: fix potential UAF in is_valid_oplock_break()
---
Results of testing on various branches:
| Branch | Patch Apply | Build Test |
|---------------------------|-------------|------------|
| stable/linux-5.15.y | Success | Success |
prev parent reply other threads:[~2025-04-15 21:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-15 2:02 [PATCH 5.15.y] smb: client: fix potential UAF in is_valid_oplock_break() Cliff Liu
2025-04-15 21:43 ` 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=20250415112449-0d403bda217b21ea@stable.kernel.org \
--to=sashal@kernel.org \
--cc=donghua.liu@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 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.