linux-kernel - Re: [PATCH] char random: fix boot id uniqueness race (v2)

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] [day] [month] [year] [list]

Date:	Wed, 15 Feb 2012 15:08:26 +0100
From:	Eric Dumazet <eric.dumazet@...il.com>
To:	Mathieu Desnoyers <mathieu.desnoyers@...icios.com>
Cc:	Theodore Ts'o <tytso@....edu>, linux-kernel@...r.kernel.org,
	Matt Mackall <mpm@...enic.com>,
	Greg Kroah-Hartman <greg@...ah.com>
Subject: Re: [PATCH] char random: fix boot id uniqueness race (v2)

Le mercredi 15 février 2012 à 08:35 -0500, Mathieu Desnoyers a écrit :

> That would make sense, as long as we're OK about turning a read-mostly
> operation into a fully serialized operation that requires to exchange
> the lock between processor cache-lines. But as you point out, it should
> be fairly unfrequently used.
> 
> Any particular reason to use a spin lock rather than a mutex ? I did put
> a mutex in my implementation assuming that it would be a little more
> RT-friendly.

generate_random_uuid(uuid) is very fast and doesnt sleep.



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