linux-kernel - Re: mount --no-canonical seems broken.

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

Message-ID: <519AB20D.7030503@tlinx.org>
Date:	Mon, 20 May 2013 16:30:21 -0700
From:	Linda Walsh <lkml@...nx.org>
To:	Karel Zak <kzak@...hat.com>
CC:	util-linux@...r.kernel.org,
	Linux-Kernel <linux-kernel@...r.kernel.org>
Subject: Re: mount --no-canonical seems broken.




Karel Zak wrote:
>
> The problem is that "mount" (without options) prints always canonicalized 
> paths (and in this case --no-canonicalize has no effect, this option
> is used for mounting only). It means if you have non-canonical paths
> in /etc/mtab then "mount" still prints canonical paths. I can fix it
> and make the output sensitive to --no-canonicalize option too.
>
> Anyway, use findmnt, it provides but complete control on the output.
>
>     Karel
>   
----
    Sure give better control, but not as widely known as "df" or "mount".

I might point out that by default,
> findmnt /

TARGET SOURCE    FSTYPE OPTIONS
/      /dev/root xfs    rw,nodiratime,relatime,attr2,inode64,noquota
> > l /dev/root
ls: cannot access /dev/root: No such file or directory

-----
It's not a device in /dev/ nor is it in /proc/devices.

Conversely, 

klogd 1.4.1, log source = ksyslog started.
[    0.000000] Initializing cgroup subsys cpuset
[    0.000000] Initializing cgroup subsys cpu
[    0.000000] Linux version 3.9.0-Isht-Van (law@...tar) (gcc version
4.7.2 20130205 [gcc-4_7-branch revision 195759] (SUSE Linux) ) #6 SMP
PREEMPT Wed May 8 17:28:40 PDT 2013
[    0.000000] Command line: BOOT_IMAGE=390-Isht-Van rw root=/dev/sdc1
root=/dev/sdc1 showopts console=ttyS0,115200n8 console=tty0 elevator=cfq
pcie_aspm=force pcie_ports=native reboot=bios

The kernel seems to know the root image at boot (even told twice from
this output!)

Not to mention, there is some comment in the kernel-related code of using
/dev/root because there is no writable storage available... even though
the command line
shows that root is mounted 'rw'...



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