From: Greg KH <gregkh@linuxfoundation.org>
To: Jiping Ma <jiping.ma2@windriver.com>
Cc: sashal@kernel.org, michael.bommarito@gmail.com,
stable@vger.kernel.org, stfrench@microsoft.com
Subject: Re: [PATCH 5.15.y] smb: client: validate the whole DACL before rewriting it in cifsacl
Date: Wed, 27 May 2026 10:14:58 +0200 [thread overview]
Message-ID: <2026052742-earlobe-reactor-47ae@gregkh> (raw)
In-Reply-To: <20260526015822.4076817-1-jiping.ma2@windriver.com>
On Tue, May 26, 2026 at 01:58:22AM +0000, Jiping Ma wrote:
> Hi,
>
> I can not find this patch in queue-5.15 and queue-6.1 of https://git.kernel.org/pub/scm/linux/kernel/git/stable/stable-queue.git,
> Do you know what happened to this patch for Linux 5.15 and Linux 6.1?
What is the git id of the commit you are looking for?
thanks,
greg k-h
prev parent reply other threads:[~2026-05-27 8:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-24 9:42 FAILED: patch "[PATCH] smb: client: validate the whole DACL before rewriting it in" failed to apply to 5.15-stable tree gregkh
2026-04-25 0:37 ` [PATCH 5.15.y] smb: client: validate the whole DACL before rewriting it in cifsacl Sasha Levin
2026-05-26 1:58 ` Jiping Ma
2026-05-27 8:14 ` Greg KH [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=2026052742-earlobe-reactor-47ae@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=jiping.ma2@windriver.com \
--cc=michael.bommarito@gmail.com \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
--cc=stfrench@microsoft.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