linux-kernel - Re: Crypto Fixes for 3.3

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+55aFwQ=KybWO6cgQLsWajF2-S9ndh2um_qmA8VP-mmdRCH7Q@mail.gmail.com>
Date:	Wed, 25 Jan 2012 20:16:54 -0800
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Herbert Xu <herbert@...dor.apana.org.au>
Cc:	"David S. Miller" <davem@...emloft.net>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Linux Crypto Mailing List <linux-crypto@...r.kernel.org>
Subject: Re: Crypto Fixes for 3.3

On Wed, Jan 25, 2012 at 8:07 PM, Herbert Xu <herbert@...dor.apana.org.au> wrote:
>
> Oops, I had incorrectly applied the first patch in the thread.
>
> I've fixed it in the tree now.

Oh well, I already pulled your tree. I just wanted to voice a few
comments on it.

>> We also avoid the problem with absolutely horrible gcc register usage
>> by having an arch-specific "accessor macro":
>
> We could certainly do something like that.  Although I'd be
> more comfortable with pushing this through linux-next, OK?

Absolutely.

               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/