linux-kernel - Re: [stable] [PATCH] KEYS: Return more accurate error codes

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] [day] [month] [year] [list]

Message-ID: <20100524214356.GH16655@kroah.com>
Date:	Mon, 24 May 2010 14:43:56 -0700
From:	Greg KH <greg@...ah.com>
To:	James Morris <jmorris@...ei.org>
Cc:	David Howells <dhowells@...hat.com>, keyrings@...ux-nfs.org,
	Dan Carpenter <error27@...il.com>,
	linux-security-module@...r.kernel.org,
	linux-kernel@...r.kernel.org, torvalds@...l.org,
	Oleg Nesterov <oleg@...hat.com>,
	Andrew Morton <akpm@...ux-foundation.org>, stable@...nel.org
Subject: Re: [stable] [PATCH] KEYS: Return more accurate error codes

On Tue, May 18, 2010 at 08:51:43AM +1000, James Morris wrote:
> On Mon, 17 May 2010, David Howells wrote:
> 
> > From: Dan Carpenter <error27@...il.com>
> > 
> > We were using the wrong variable here so the error codes weren't being returned
> > properly.  The original code returns -ENOKEY.
> > 
> > Signed-off-by: Dan Carpenter <error27@...il.com>
> > Signed-off-by: David Howells <dhowells@...hat.com>
> 
> Queued for Linus -- is also likely a -stable candidate.

If so, please just put a:
	Cc: stable <stable@...nel.org>
to the signed-off-by area of the patch.  That way I automatically get
notified when it goes into Linus's tree, and I don't have to go dig and
try to match up a random email reference like this one with the actual
patch in Linus's tree...

thanks,

greg k-h
--
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/