On Mon, Sep 23, 2019 at 8:31 PM Micah Morton <mort...@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
