Re: Forcing a more random uuid (random seed bug)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Followup to:  <200502021433.42108.niccolo@xxxxxxxxx>
By author:    Niccolo Rigacci <niccolo@xxxxxxxxx>
In newsgroup: linux.dev.raid
>
> > I get /dev/md5, /dev/md6, /dev/md7
> > and /dev/md8 all with the same UUID!
> 
> It seems that there is a bug in mdadm: when generating the UUID for a 
> volume, the random() function is called, but the random sequence is never 
> initialized.
> 
> The result is that every volume created with mdadm has an uuid of:
> 6b8b4567:327b23c6:643c9869:66334873
> 
> See also Debian bug 292784 at
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=292784
> 
> I fixed the problem adding the following patch to mdadm.c, but please bear 
> in mind that I'm totally unaware of mdadm code and quite naive in C 
> programming:
> 

Please don't use (s)random at all, except as a possible fallback to
/dev/(u)random.

	-hpa
-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux RAID Wiki]     [ATA RAID]     [Linux SCSI Target Infrastructure]     [Linux Block]     [Linux IDE]     [Linux SCSI]     [Linux Hams]     [Device Mapper]     [Device Mapper Cryptographics]     [Kernel]     [Linux Admin]     [Linux Net]     [GFS]     [RPM]     [git]     [Yosemite Forum]


  Powered by Linux