linux-kernel - Re: [PATCH, RFC 07/12] random: allow architectures to optionally define random_get

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: <20130923110531.GI7321@thunk.org>
Date:	Mon, 23 Sep 2013 07:05:31 -0400
From:	Theodore Ts'o <tytso@....edu>
To:	Stephan Mueller <smueller@...onox.de>
Cc:	Linux Kernel Developers List <linux-kernel@...r.kernel.org>,
	hpa@...or.com, joern@...fs.org, macro@...ux-mips.org,
	ralf@...ux-mips.org, dave.taht@...il.com, blogic@...nwrt.org,
	andrewmcgr@...il.com, geert@...ux-m68k.org, tg@...bsd.de
Subject: Re: [PATCH, RFC 07/12] random: allow architectures to optionally
 define random_get_entropy()

On Mon, Sep 23, 2013 at 12:38:26PM +0200, Stephan Mueller wrote:
> 
> Are there any plans to get such function implemented on large list of 
> architectures without a get_cycles function?

For some architectures, yes.  As John Stultz pointed out, on many of
the older embedded platforms (which are many of the ones with out a
get_cycles function), the only clocksource they have is the jiffies
time source anyway.  So I'd much rather take each architecture one at
a time, and fix them right.

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