linux-kernel - Re: [PATCH 3.4 01/25] crypto: scatterwalk - Set the chain pointer indication bit

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: <2665532.GYRAgVKg91@tlendack-t1>
Date:	Wed, 11 Dec 2013 08:51:44 -0600
From:	Tom Lendacky <thomas.lendacky@....com>
To:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>
CC:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"stable@...r.kernel.org" <stable@...r.kernel.org>,
	Herbert Xu <herbert@...dor.apana.org.au>
Subject: Re: [PATCH 3.4 01/25] crypto: scatterwalk - Set the chain pointer indication bit


On Tuesday, December 10, 2013 06:02:29 PM Greg Kroah-Hartman wrote:
> On Tue, Dec 10, 2013 at 02:46:46PM +0000, Lendacky, Thomas wrote:
> > Hi Greg,
> > 
> > This patch is probably not needed in any of the stable branches, but if
> > you do add it you'll need to also include a patch that changes the use
> > of an sg_page to an sg_chain_ptr to prevent a BUG_ON when CONFIG_DEBUG_SG
> > is enabled (http://marc.info/?l=linux-crypto-vger&m=138627061905651&w=2).
> 
> You are referring to commit 389a5390583a18e45bc4abd4439291abec5e7a63 in
> Linus's tree, right?  It's in my queue to apply after 3.13-rc4 comes

Yes, that's the one.

Thanks,
Tom

> out, but I guess it's good to add it now as it is known that this is an
> issue to be resolved.
> 
> I'll go do that right now, thanks for letting me know.
> 
> 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/