[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHk-=wjH25fp_9oMMi+1GxUR1h+WyXQRvW+GuNVq7vC9Kaad2g@mail.gmail.com>
Date: Thu, 26 Sep 2019 11:21:33 -0700
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Micah Morton <mortonm@...omium.org>
Cc: James Morris <jamorris@...uxonhyperv.com>,
Jann Horn <jannh@...gle.com>,
Bart Van Assche <bart.vanassche@....com>,
"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
linux-security-module <linux-security-module@...r.kernel.org>
Subject: Re: [GIT PULL] SafeSetID LSM changes for 5.4
On Mon, Sep 23, 2019 at 8:31 PM Micah Morton <mortonm@...omium.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
Powered by blists - more mailing lists