From: Sasha Levin <sashal@kernel.org>
To: Kees Cook <keescook@chromium.org>
Cc: Loic <hackurx@opensec.fr>, "# 3.4.x" <stable@vger.kernel.org>,
Salvatore Mesoraca <s.mesoraca16@gmail.com>,
Solar Designer <solar@openwall.com>,
Al Viro <viro@zeniv.linux.org.uk>,
Dan Carpenter <dan.carpenter@oracle.com>,
Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [PATCH] namei: allow restricted O_CREAT of FIFOs and regular files
Date: Wed, 31 Oct 2018 11:00:38 -0400 [thread overview]
Message-ID: <20181031150037.GQ194472@sasha-vm> (raw)
In-Reply-To: <CAGXu5jKLASZ_XSYtXubH6vzZN689o1MrirJncch1aY8JC8Vi6w@mail.gmail.com>
On Tue, Oct 30, 2018 at 01:28:36PM -0700, Kees Cook wrote:
>On Tue, Oct 23, 2018 at 7:37 PM, Loic <hackurx@opensec.fr> wrote:
>> Hello,
>>
>> Please picked up this patch for linux 4.9 and 4.14 (linux 4.4 needs a small modification).
>> Indeed, this code will be beneficial to the GNU/Linux distributions that use a longterm kernel.
>
>Thanks for doing these (and 4.4). It'll be nice to have this available.
>
>Reviewed-by: Kees Cook <keescook@chromium.org>
This is a hardening patch rather than something that addresses a known
issue, no? Why would it go into stable?
--
Thanks,
Sasha
next prev parent reply other threads:[~2018-10-31 23:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-23 18:37 [PATCH] namei: allow restricted O_CREAT of FIFOs and regular files Loic
2018-10-30 20:28 ` Kees Cook
2018-10-31 15:00 ` Sasha Levin [this message]
2018-10-31 16:27 ` Kees Cook
2018-10-31 20:57 ` Loic
2018-11-15 17:05 ` Sasha Levin
2018-11-15 18:26 ` Sasha Levin
2018-11-15 19:24 ` Loic
2018-11-29 12:28 ` 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=20181031150037.GQ194472@sasha-vm \
--to=sashal@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=dan.carpenter@oracle.com \
--cc=hackurx@opensec.fr \
--cc=keescook@chromium.org \
--cc=s.mesoraca16@gmail.com \
--cc=solar@openwall.com \
--cc=stable@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=viro@zeniv.linux.org.uk \
/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