[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHC9VhSSwYk6isqz8N3nOO_O17C30E2EyCHKf5OqsdESeMoT7g@mail.gmail.com>
Date: Sat, 11 May 2019 14:13:09 -0400
From: Paul Moore <paul@...l-moore.com>
To: Linus Torvalds <torvalds@...ux-foundation.org>,
James Morris <jmorris@...ei.org>
Cc: LSM List <linux-security-module@...r.kernel.org>,
Linux List Kernel Mailing <linux-kernel@...r.kernel.org>
Subject: Re: [GIT PULL] security subsystem: Tomoyo updates for v5.2
On Sat, May 11, 2019 at 10:38 AM Linus Torvalds
<torvalds@...ux-foundation.org> wrote:
> On Fri, May 10, 2019 at 6:09 PM James Morris <jmorris@...ei.org> wrote:
> >
> > These patches include fixes to enable fuzz testing, and a fix for
> > calculating whether a filesystem is user-modifiable.
>
> So now these have been very recently rebased (on top of a random
> 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.
If it helps, the process I use for the SELinux and audit trees is
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
--
paul moore
www.paul-moore.com
Powered by blists - more mailing lists