mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Eric Dumazet <eric.dumazet@gmail.com>
To: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Cc: "Theodore Ts'o" <tytso@mit.edu>, Matt Mackall <mpm@selenic.com>,
	Greg Kroah-Hartman <greg@kroah.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] char random: fix boot id uniqueness race (v3)
Date: Wed, 15 Feb 2012 19:50:47 +0100	[thread overview]
Message-ID: <1329331847.2469.2.camel@edumazet-laptop> (raw)
In-Reply-To: <20120215184044.GB19182@Krystal>

Le mercredi 15 février 2012 à 13:40 -0500, Mathieu Desnoyers a écrit :
> The proc file /proc/sys/kernel/random/boot_id can be read concurrently
> by user-space processes. If two (or more) user-space processes
> concurrently read boot_id when sysctl_bootid is not yet assigned, a race
> can occur making boot_id differ between the reads. Because the whole
> point of the boot id is to be unique across a kernel execution, fix this
> by protecting this operation with a spinlock.
> 
> Given that this operation is not frequently used, hitting the spinlock
> on each call should not be an issue.
> 
> * Changelog since v1:
> - boot_id_mutex is now declared within the proc_do_uuid scope.
> - added explanation for memory barriers.
> 
> * Changelog since v2:
> - simplify: use spinlock on all paths, suggested by Eric Dumazet.
> 
> Signed-off-by: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
> CC: "Theodore Ts'o" <tytso@mit.edu>
> CC: Matt Mackall <mpm@selenic.com>
> CC: Eric Dumazet <eric.dumazet@gmail.com>
> CC: Greg Kroah-Hartman <greg@kroah.com>
> ---
>  drivers/char/random.c |   11 ++++++++---
>  1 file changed, 8 insertions(+), 3 deletions(-)
> 
> Index: linux-2.6-lttng/drivers/char/random.c
> ===================================================================
> --- linux-2.6-lttng.orig/drivers/char/random.c
> +++ linux-2.6-lttng/drivers/char/random.c
> @@ -1250,10 +1250,15 @@ static int proc_do_uuid(ctl_table *table
>  	uuid = table->data;
>  	if (!uuid) {
>  		uuid = tmp_uuid;
> -		uuid[8] = 0;
> -	}
> -	if (uuid[8] == 0)
>  		generate_random_uuid(uuid);
> +	} else {
> +		static DEFINE_SPINLOCK(bootid_spinlock);
> +
> +		spin_lock(&bootid_spinlock);
> +		if (!uuid[8])
> +			generate_random_uuid(uuid);
> +		spin_unlock(&bootid_spinlock);
> +	}
>  
>  	sprintf(buf, "%pU", uuid);
>  
> 

Signed-off-by: Eric Dumazet <eric.dumazet@gmail.com>

Thanks Mathieu !



      reply	other threads:[~2012-02-15 18:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-15 18:40 Mathieu Desnoyers
2012-02-15 18:50 ` Eric Dumazet [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1329331847.2469.2.camel@edumazet-laptop \
    --to=eric.dumazet@gmail.com \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=mpm@selenic.com \
    --cc=tytso@mit.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®