From: Paul Gortmaker <paul.gortmaker@windriver.com>
To: Greg KH <gregkh@linuxfoundation.org>
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: Thu, 14 Dec 2023 23:18:36 -0500 [thread overview]
Message-ID: <ZXvTnMWF/G/RrthX@windriver.com> (raw)
In-Reply-To: <2023121407-composed-unscathed-5081@gregkh>
[Re: [PATCH 0/1] RFC: linux-5.15.y ksmbd backport for CVE-2023-38431] On 14/12/2023 (Thu 09:20) Greg KH wrote:
[...]
> > > If no one steps up, I'll just mark the thing as broken, it is _so_ far
> > > behind in patches that it's just sad.
> >
> > Again, in this case - I have no problem with that - but as a note of
> > record -- whenever linux-stable removes a Kconfig, either explicitly or
> > by a depends on BROKEN - it does trigger fallout for some people.
>
> In what way? Just having to update default config options?
>
> > The Yocto/OE does an audit on the Kconfig output looking for options
> > that were explicitly set (or un-set) by the user, or by base templates.
> > If they don't land in the final .config file -- it lets you know.
>
> So defconfig type checks?
Here is a recent example.
https://lists.yoctoproject.org/g/linux-yocto/message/13387
I am not saying linux-stable is wrong to do these kinds of changes, I'm
just saying there is an impact that people might not be aware of.
Paul.
--
>
> thanks,
>
> greg k-h
next prev parent reply other threads:[~2023-12-15 4:18 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 ` [PATCH 0/1] RFC: linux-5.15.y ksmbd backport for CVE-2023-38431 Greg KH
2023-12-12 20:13 ` [EXTERNAL] " 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 [this message]
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=ZXvTnMWF/G/RrthX@windriver.com \
--to=paul.gortmaker@windriver.com \
--cc=gregkh@linuxfoundation.org \
--cc=linkinjeon@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 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.