linux-kernel - Re: [PATCH] clarify a usage constraint for cnt32_to

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <21293.1292863890@redhat.com>
Date:	Mon, 20 Dec 2010 16:51:30 +0000
From:	David Howells <dhowells@...hat.com>
To:	Nicolas Pitre <nico@...xnic.net>
Cc:	dhowells@...hat.com,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	lkml <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] clarify a usage constraint for cnt32_to_63()

Nicolas Pitre <nico@...xnic.net> wrote:

> The cnt32_to_63 algorithm relies on proper counter data evaluation
> ordering to work properly. This was missing from the provided
> documentation.
> 
> Let's augment the documentation with the missing usage constraint and
> fix the only instance that got it wrong.
> 
> Signed-off-by: Nicolas Pitre <nico@...xnic.net>
> Cc: David Howells <dhowells@...hat.com>

Seems to work on my ASB2305.

Acked-by: David Howells <dhowells@...hat.com>

--
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/