From: Kyle Huey <me@kylehuey.com>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: gregkh@linuxfoundation.org,
"Robert O'Callahan" <robert@ocallahan.org>,
Kees Cook <keescook@chromium.org>, Kyle Huey <khuey@kylehuey.com>,
Oliver Sang <oliver.sang@intel.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] signal: Don't always set SA_IMMUTABLE for forced signals" failed to apply to 5.15-stable tree
Date: Sun, 28 Nov 2021 22:23:38 -0800 [thread overview]
Message-ID: <CAP045ApWgeLtpGXjEt8DvH1uGJ-2vEo1zq-0EzFcR6F+HNoj7Q@mail.gmail.com> (raw)
In-Reply-To: <87y25ef82b.fsf@email.froward.int.ebiederm.org>
On Tue, Nov 23, 2021 at 9:15 PM Eric W. Biederman <ebiederm@xmission.com> wrote:
>
> Kyle Huey <me@kylehuey.com> writes:
>
>
> > Since this is taken care of now, AFAICT, I do have one additional
> > question. I reported the regression to LKML a day or so before 5.15.3
> > was cut. What should I have noticed to see that the regressing
> > changeset was going to 5.15 and where should I have said "hey please
> > don't ship this on 5.15 yet"?
> >
> > I'd like to know what to do next time :)
> >
> When patches are added to the stable tree they are posted
> for review.
>
> I was Cc'd on a couple of them because of this discussion. The list
> appear to be "<stable-commits@vger.kernel.org>". Feedback is requested
> to go to "<stable@vger.kernel.org>". So I believe this conversation is
> enough to remove the unnecessary patches before they make it to a stable
> release.
>
> The boiler plate looks like:
> > Cc: <stable-commits@vger.kernel.org>
> > Date: Tue, 23 Nov 2021 19:11:53 +0100 (10 hours, 58 minutes, 56 seconds ago)
> >
> >
> > This is a note to let you know that I've just added the patch titled
> >
> > exit/syscall_user_dispatch: Send ordinary signals on failure
> >
> > to the 5.15-stable tree which can be found at:
> > http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
> >
> > The filename of the patch is:
> > exit-syscall_user_dispatch-send-ordinary-signals-on-failure.patch
> > and it can be found in the queue-5.15 subdirectory.
> >
> > If you, or anyone else, feels it should not be added to the stable tree,
> > please let <stable@vger.kernel.org> know about it.
>
>
> I hope that helps.
>
> Eric
So if I understand this correctly the best (or maybe even only) way to
stop a regressing changeset from making it into a stable release is to
separately search/watch the stable mailing list for the changeset in
question?
- Kyle
next prev parent reply other threads:[~2021-11-29 6:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-22 12:31 FAILED: patch "[PATCH] signal: Don't always set SA_IMMUTABLE for forced signals" failed to apply to 5.15-stable tree gregkh
2021-11-23 15:08 ` Kyle Huey
2021-11-23 17:29 ` Thomas Backlund
2021-11-23 18:12 ` Greg KH
2021-11-23 19:24 ` Eric W. Biederman
2021-11-23 20:00 ` Eric W. Biederman
2021-11-23 20:00 ` Thomas Backlund
2021-11-23 21:41 ` Eric W. Biederman
2021-11-23 21:56 ` Thomas Backlund
2021-11-24 1:33 ` Kyle Huey
2021-11-24 5:15 ` Eric W. Biederman
2021-11-29 6:23 ` Kyle Huey [this message]
2021-11-29 6:43 ` Greg KH
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=CAP045ApWgeLtpGXjEt8DvH1uGJ-2vEo1zq-0EzFcR6F+HNoj7Q@mail.gmail.com \
--to=me@kylehuey.com \
--cc=ebiederm@xmission.com \
--cc=gregkh@linuxfoundation.org \
--cc=keescook@chromium.org \
--cc=khuey@kylehuey.com \
--cc=oliver.sang@intel.com \
--cc=robert@ocallahan.org \
--cc=stable@vger.kernel.org \
--cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).