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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5148F1F7.7080706@zytor.com>
Date:	Tue, 19 Mar 2013 16:17:11 -0700
From:	"H. Peter Anvin" <hpa@...or.com>
To:	William Hubbs <williamh@...too.org>
CC:	linux-kernel@...r.kernel.org, w.d.hubbs@...il.com, rob@...dley.net,
	mpagano@...too.org, ryao@...too.org, gregkh@...too.org,
	torvalds@...ux-foundation.org
Subject: Re: [PATCH] init: fix name of root device in /proc/mounts

On 03/19/2013 03:28 PM, William Hubbs wrote:
> All,
> 
> I haven't heard any more on this patch, so I wanted to ping the
> thread again and find out the status.
> 
> The original message is linked below[1].
> 
> The issue is that /dev/root appears in /proc/mounts if you do not
> boot with an initramfs, but /dev/root is not a device node. In the
> past, udev created a symbolic link from /dev/root to the
> appropriate block device, but it does not do this any longer. Also,
> devtmpfs does not create this symbolic link.
> 
> This is causing bugs with software that depends on the existence
> of /dev/root [2] for example.
> 
> Do you need any more information on this patch, or is there some
> reason it can't go in?
> 

Seems okay to me, although even better would be to use the udev name
of the device in question.

	-hpa

-- 
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel.  I don't speak on their behalf.

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ