From: Linus Torvalds <torvalds@linux-foundation.org>
To: Micah Morton <mortonm@chromium.org>
Cc: James Morris <jamorris@linuxonhyperv.com>,
Jann Horn <jannh@google.com>,
Bart Van Assche <bart.vanassche@wdc.com>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-security-module <linux-security-module@vger.kernel.org>
Subject: Re: [GIT PULL] SafeSetID LSM changes for 5.4
Date: Thu, 26 Sep 2019 11:21:33 -0700 [thread overview]
Message-ID: <CAHk-=wjH25fp_9oMMi+1GxUR1h+WyXQRvW+GuNVq7vC9Kaad2g@mail.gmail.com> (raw)
In-Reply-To: <CAJ-EccMy=tNPp3=PQZxLT7eovojoAdpfQmqhAyv7XO3GwPQBMg@mail.gmail.com>
On Mon, Sep 23, 2019 at 8:31 PM Micah Morton <mortonm@chromium.org> wrote:
>
> The best way I know of ensuring this is
> for me to personally run the SafeSetID selftest (in
> tools/testing/selftests/safesetid/) every release, regardless of
> whether we make any changes to SafeSetID itself. Does this sound
> sufficient or are there more formal guidelines/processes here that I'm
> not aware of?
I think that would help, but I wopuld also hope that somebody actually
runs Chromium / Chrome OS with a modern kernel.
Even if *standard* device installs don't end up having recent kernels,
I would assume there are people who are testing development setups?
Linus
next prev parent reply other threads:[~2019-09-26 18:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-18 17:41 [GIT PULL] SafeSetID LSM changes for 5.4 Micah Morton
2019-09-23 19:01 ` Linus Torvalds
2019-09-23 19:28 ` Linus Torvalds
2019-09-23 23:35 ` James Morris
2019-09-24 0:45 ` Linus Torvalds
2019-09-24 3:30 ` Micah Morton
2019-09-26 18:21 ` Linus Torvalds [this message]
2019-09-23 23:30 ` Paul E. McKenney
2019-09-24 0:44 ` Linus Torvalds
2019-10-21 6:58 ` Ingo Molnar
2019-10-22 2:13 ` Paul E. McKenney
2019-09-23 19:05 ` pr-tracker-bot
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='CAHk-=wjH25fp_9oMMi+1GxUR1h+WyXQRvW+GuNVq7vC9Kaad2g@mail.gmail.com' \
--to=torvalds@linux-foundation.org \
--cc=bart.vanassche@wdc.com \
--cc=jamorris@linuxonhyperv.com \
--cc=jannh@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=mortonm@chromium.org \
--cc=paulmck@linux.vnet.ibm.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;
as well as URLs for NNTP newsgroup(s).