From: Greg KH <gregkh@linuxfoundation.org>
To: paul.gortmaker@windriver.com
Cc: Namjae Jeon <linkinjeon@kernel.org>,
Steve French <stfrench@microsoft.com>,
stable@vger.kernel.org
Subject: Re: [PATCH 0/1] RFC: linux-5.15.y ksmbd backport for CVE-2023-38431
Date: Tue, 12 Dec 2023 21:04:38 +0100 [thread overview]
Message-ID: <2023121241-pope-fragility-edad@gregkh> (raw)
In-Reply-To: <20231212184745.2245187-1-paul.gortmaker@windriver.com>
On Tue, Dec 12, 2023 at 01:47:44PM -0500, paul.gortmaker@windriver.com wrote:
> From: Paul Gortmaker <paul.gortmaker@windriver.com>
>
> This is a bit long, but I've never touched this code and all I can do is
> compile test it. So the below basically represents a capture of my
> thought process in fixing this for the v5.15.y-stable branch.
Nice work, but really, given that there are _SO_ many ksmb patches that
have NOT been backported to 5.15.y, I would strongly recommend that we
just mark the thing as depending on BROKEN there for now as your one
backport here is not going to make a dent in the fixes that need to be
applied there to resolve the known issues that the codebase currently
has resolved in newer kernels.
Do you use this codebase on 5.15.y? What drove you to want to backport
this, just the presence of a random CVE identifier? If that's all it
takes to get companies to actually do backports, maybe I should go
allocate more of them :)
thanks,
greg k-h
next prev parent reply other threads:[~2023-12-12 20:04 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-12 18:47 [PATCH 0/1] RFC: linux-5.15.y ksmbd backport for CVE-2023-38431 paul.gortmaker
2023-12-12 18:47 ` [PATCH 1/1] ksmbd: check the validation of pdu_size in ksmbd_conn_handler_loop paul.gortmaker
2023-12-13 4:59 ` Namjae Jeon
2023-12-18 10:38 ` Greg KH
2023-12-18 11:28 ` Namjae Jeon
2023-12-18 11:38 ` Greg KH
2023-12-12 20:04 ` Greg KH [this message]
2023-12-12 20:13 ` [EXTERNAL] Re: [PATCH 0/1] RFC: linux-5.15.y ksmbd backport for CVE-2023-38431 Steven French
2023-12-12 20:52 ` Paul Gortmaker
2023-12-12 21:15 ` Steven French
2023-12-13 14:36 ` Greg KH
2023-12-13 23:31 ` Namjae Jeon
2023-12-14 8:05 ` Greg KH
2023-12-14 11:33 ` Namjae Jeon
2023-12-14 11:58 ` Greg KH
2023-12-14 13:58 ` Namjae Jeon
2023-12-12 20:45 ` Paul Gortmaker
2023-12-13 14:34 ` Greg KH
2023-12-14 3:28 ` Paul Gortmaker
2023-12-14 8:20 ` Greg KH
2023-12-15 4:18 ` Paul Gortmaker
2023-12-13 5:13 ` Namjae Jeon
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=2023121241-pope-fragility-edad@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=linkinjeon@kernel.org \
--cc=paul.gortmaker@windriver.com \
--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