From: Greg KH <greg@kroah.com>
To: linux-kernel@vger.kernel.org
Cc: oleg@redhat.com, stable-commits@vger.kernel.org
Subject: Re: Patch "ipc/mqueue.c: change __do_notify() to bypass check_kill_permission()" has been added to the 4.14-stable tree
Date: Wed, 13 May 2020 08:42:57 +0200 [thread overview]
Message-ID: <20200513064257.GA762447@kroah.com> (raw)
In-Reply-To: <20200513005117.D244020753@mail.kernel.org>
On Tue, May 12, 2020 at 08:51:16PM -0400, Sasha Levin wrote:
> This is a note to let you know that I've just added the patch titled
>
> ipc/mqueue.c: change __do_notify() to bypass check_kill_permission()
>
> to the 4.14-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:
> ipc-mqueue.c-change-__do_notify-to-bypass-check_kill.patch
> and it can be found in the queue-4.14 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.
Nope, this breaks the build for 4.14, so I've dropped it.
greg k-h
parent reply other threads:[~2020-05-13 6:43 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20200513005117.D244020753@mail.kernel.org>]
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=20200513064257.GA762447@kroah.com \
--to=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oleg@redhat.com \
--cc=stable-commits@vger.kernel.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