linux-kernel - Re: [21/28] crypto: sha512 - Avoid stack bloat on i386

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: <20120217023742.GA21909@kroah.com>
Date:	Thu, 16 Feb 2012 18:37:42 -0800
From:	Greg KH <gregkh@...uxfoundation.org>
To:	Herbert Xu <herbert@...dor.apana.org.au>
Cc:	David Miller <davem@...emloft.net>, linux-kernel@...r.kernel.org,
	stable@...r.kernel.org, torvalds@...ux-foundation.org,
	akpm@...ux-foundation.org, alan@...rguk.ukuu.org.uk
Subject: Re: [21/28] crypto: sha512 - Avoid stack bloat on i386

On Fri, Feb 17, 2012 at 01:28:06PM +1100, Herbert Xu wrote:
> On Thu, Feb 16, 2012 at 06:17:18PM -0800, Greg KH wrote:
> > On Thu, Feb 16, 2012 at 08:52:31PM -0500, David Miller wrote:
> > > From: Greg KH <gregkh@...uxfoundation.org>
> > > Date: Thu, 16 Feb 2012 16:55:55 -0800
> > > 
> > > > 3.2-stable review patch.  If anyone has any objections, please let me know.
> > > 
> > > This causes a stack usage regression on sparc that Herbert
> > > is in the middle of merging a fix for into Linus's tree.
> > 
> > Ick.  Any idea when that will hit Linus's tree?  If it's before next
> > Monday, we are good, and I can queue it up here, if not, then I'll drop
> > this and have to add it back later.
> 
> I've pushed it though it hasn't been pulled yet:
> 
> The commit ID is f2ea0f5f04c97b48c88edccba52b0682fbe45087.

Thanks, I'll watch out for it.

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/