lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CA+55aFwBXZn9QizRAHNWQXuj6vE1Z9jrMDKVtQmoFZUH=yRf5A@mail.gmail.com>
Date:	Mon, 11 Mar 2013 15:15:36 -0700
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	Greg KH <gregkh@...uxfoundation.org>,
	James Morris <jmorris@...ei.org>,
	David Howells <dhowells@...hat.com>, keyrings@...ux-nfs.org,
	Petr Matousek <pmatouse@...hat.com>,
	"security@...nel.org" <security@...nel.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	mguzik@...hat.com, Ben Hutchings <ben@...adent.org.uk>
Subject: Re: [PATCH] KEYS: Fix race with concurrent install_user_keyrings()

On Mon, Mar 11, 2013 at 2:10 PM, Andrew Morton
<akpm@...ux-foundation.org> wrote:
> On Mon, 11 Mar 2013 14:02:11 -0700 Greg KH <gregkh@...uxfoundation.org> wrote:
>
>> On Thu, Mar 07, 2013 at 03:59:09PM +1100, James Morris wrote:
>> > On Wed, 6 Mar 2013, David Howells wrote:
>> >
>> > > Reported-by: Mateusz Guzik <mguzik@...hat.com>
>> > > Signed-off-by: David Howells <dhowells@...hat.com>
>> >
>> > Acked-by: James Morris <james.l.morris@...cle.com>
>>
>> What happened to this patch?  I don't see it in Linus's tree, James, did
>> you pick it up?
>
> James has acked it.  I have it queued for processing so it isn't lost.
> It has no cc:stable's in it, but David always forgets that ;)

I usually expect that if the subsystem maintainer is involved, he's
the one to pick it up.

If James' ack was "Linus, please take this directly, I'm busy and have
nothing else pending", then I really would prefer to hear that exact
thing. Otherwise I'm just going to ignore the patch "safe" in the
knowledge that clearly the subsystem maintainer is aware of it.

             Linus
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ