On Sat, May 11, 2019 at 10:38 AM Linus Torvalds
<torvalds@xxxxxxxxxxxxxxxxxxxx> wrote:
On Fri, May 10, 2019 at 6:09 PM James Morris <jmorris@xxxxxxxxx> wrote:If it helps, the process I use for the SELinux and audit trees is
These patches include fixes to enable fuzz testing, and a fix forSo now these have been very recently rebased (on top of a random
calculating whether a filesystem is user-modifiable.
merge-window "tree of the day" version) instead of having multiple
merges.
That makes the history cleaner, but has its own issues.
We really need to find a different model for the security layer patches.
documented below. While it's far from perfect (I still don't like
basing the -next trees on -rcX releases) it has seemed to work
reasonably well for some time now.
* https://github.com/SELinuxProject/selinux-kernel/blob/master/README.md