# Re: \[GIT PULL\] SafeSetID LSM changes for 5.4

- From: Linus Torvalds \<torvalds@linux-foundation.org\>
- Date: 2019-09-26 18:21:55 
- List: linux-security-module
- Page: https://ratatoskr.run/linux-security-module/2019/09/5727591
- Thread: https://ratatoskr.run/linux-security-module/2019/09/5720254/t.md

```text
On Mon, Sep 23, 2019 at 8:31 PM Micah Morton [ref] 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
```