From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: Sasha Levin <sashal@kernel.org>,
gregkh@linuxfoundation.org, linkinjeon@kernel.org,
sfrench@samba.org, stfrench@microsoft.com,
senozhatsky@chromium.org, tom@talpey.com, mmakassikis@freebox.fr,
linux-cifs@vger.kernel.org, jsingh@cloudlinux.com
Subject: Re: [PATCH 6.1.y] ksmbd: fix NULL pointer dereference in opinfo_put()
Date: Sat, 14 Nov 2026 12:42:14 -0500 [thread overview]
Message-ID: <draft-agent5-0003-re-ksmbd-opinfo-put-61@kernel.org> (raw)
In-Reply-To: <20261114114943.5122-1-jsingh@cloudlinux.com>
On 2026-11-14, Jaskaran Singh <jsingh@cloudlinux.com> wrote:
> The problem does not exist upstream; this fix is for 6.1.y only.
Thanks. Since this has no upstream commit and only exists for 6.1.y, I would
like an ack from the ksmbd maintainers before queueing it.
Namjae, could you take a look?
--
Thanks,
Sasha
prev parent reply other threads:[~2026-11-14 17:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-14 11:49 [PATCH 6.1.y] ksmbd: fix NULL pointer dereference in opinfo_put() Jaskaran Singh
2026-11-14 17:42 ` 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=draft-agent5-0003-re-ksmbd-opinfo-put-61@kernel.org \
--to=sashal@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=jsingh@cloudlinux.com \
--cc=linkinjeon@kernel.org \
--cc=linux-cifs@vger.kernel.org \
--cc=mmakassikis@freebox.fr \
--cc=senozhatsky@chromium.org \
--cc=sfrench@samba.org \
--cc=stable@vger.kernel.org \
--cc=stfrench@microsoft.com \
--cc=tom@talpey.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