linux-kernel - Re: 3.5-rcX : Big problem with root device returning

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]

Message-ID: <4FFF0C8D.5000409@msgid.tls.msk.ru>
Date:	Thu, 12 Jul 2012 21:42:37 +0400
From:	Michael Tokarev <mjt@....msk.ru>
To:	werner <w.landgraf@...ru>
CC:	linux-kernel@...r.kernel.org
Subject: Re: 3.5-rcX : Big problem with root device returning

On 12.07.2012 16:08, werner wrote:
> There is a big problem since 3.5-rc1 which potentially mess the installations
> 
> rdev   don't give longer back the root device like /dev/sda1  , but in the bios form like 0x80010300

Note rdev returns information which is written to kernel image, not
information about actual device the system booted from.

> rdev is essential for the installation programs  and for the installation f.ex. of lilo .   It's not conveniente to rely on the bios numbers, because on some meinbords they change depending which boot order you select in BIOS, or only if you select another boot device in the bios boot menu with F12.   Whilst /dev/sdXY is more reliable.
> 
>   rdev is an old basical function which always worked correctly, until now.

rdev utility is obsolete, it is not present in current util-linux anymore,
because it makes just no sense nowadays.  Storing root device in the
kernel image has been obsoleted long ago by boot loaders providing
kernel command line and root= parameter.  More, root device is often
not mounted by kernel itself, but by initramfs (which become an integral
part of the kernel image).

It is obsolete because of 3 reasons:

1) you've kernel command line from the bootloader to store this and
  other info
2) it is not guaranteed that the next reboot the same device will be
 using the same /dev/sdX node, since they're discovered dynamically
 (in this sense, bios codes are more reliable, and filesystem UUIDs or
 labels are the right way to go)
3) static device numbers are slowly going away too, very few tools
 left which knows about particular major,minor pairs.

> The error starts with 3.5-rc1 and is not corrected until 3.5-rc6 .    If I go back to an earlier kernel, 3.4 or older, then the same installation works correct (rdev gives /dev/sda1 ) and if I go back then again to 3.5-rcX it's again wrong (rdev gives 0x80010300).    Thus, this seems a wrong manner how the kernel gives back the root device,  or interact with rdev.      It's also possible that this problem happens only under any kernel compilation option,   so that below I give the differences in config between 3.4 and 3.5-rc1
> 
> This problem should be fixed most quickly,  rdev always have to work correctly.

There's no problem, so nothing to fix.

Thanks,

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