[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHk-=wiFti6=K2fyAYhx-PSX9ovQPJUNp0FMdV0pDaO_pSx9MQ@mail.gmail.com>
Date: Wed, 10 Jul 2019 18:59:05 -0700
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Linus Torvalds <torvalds@...ux-foundation.org>,
David Howells <dhowells@...hat.com>,
James Morris <jmorris@...ei.org>, keyrings@...r.kernel.org,
Netdev <netdev@...r.kernel.org>, linux-nfs@...r.kernel.org,
CIFS <linux-cifs@...r.kernel.org>, linux-afs@...ts.infradead.org,
linux-fsdevel <linux-fsdevel@...r.kernel.org>,
linux-integrity@...r.kernel.org,
LSM List <linux-security-module@...r.kernel.org>,
Linux List Kernel Mailing <linux-kernel@...r.kernel.org>
Subject: Re: [GIT PULL] Keys: Set 4 - Key ACLs for 5.3
On Wed, Jul 10, 2019 at 1:15 PM Eric Biggers <ebiggers@...nel.org> wrote:
>
> Also worth noting that the key ACL patches were only in linux-next for 9 days
> before the pull request was sent.
Yes. I was not entirely happy with the whole key subsystem situation.
See my concerns in
https://lore.kernel.org/lkml/CAHk-=wjEowdfG7v_4ttu3xhf9gqopj1+q1nGG86+mGfGDTEBBg@mail.gmail.com/
for more. That was before I realized it was buggy.
So it really would be good to have more people involved, and more
structure to the keys development (and, I suspect, much else under
security/)
Anyway, since it does seem like David is offline, I've just reverted
this from my tree, and will be continuing my normal merge window pull
requests (the other issues I have seen have fixes in their respective
trees).
Linus
Powered by blists - more mailing lists