| 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
| ||
|
Date: Thu, 28 Jun 2007 11:36:16 -0400 From: "H. Peter Anvin" <hpa@...or.com> To: Pavel Machek <pavel@....cz> CC: Al Viro <viro@....linux.org.uk>, Linux Kernel Mailing List <linux-kernel@...r.kernel.org>, linux-fsdevel@...r.kernel.org, util-linux-ng@...r.kernel.org Subject: Re: Adding subroot information to /proc/mounts, or obtaining that through other means Pavel Machek wrote: > Hi! > >>> ... or, alternatively, add a subfield to the first field (which would >>> entail escaping whatever separator we choose): >>> >>> /dev/md6 /export ext3 rw,data=ordered 0 0 >>> /dev/md6:/users/foo /home/foo ext3 rw,data=ordered 0 0 >>> /dev/md6:/users/bar /home/bar ext3 rw,data=ordered 0 0 >> Hell, no. The first field is in principle impossible to parse unless >> you know the fs type. >> >> How about making a new file with sane format? From the very > > Well, what about /sysfs, with its one value per file rule? > There are two reasons not to do it that way: - atomicity - backwards compatibility Of these, I would argue the former is the most important. Additionally, I don't think sysfs has the ability to present different structures on a per-process basis; keep in mind this isn't really /proc/mounts, but really /proc/<pid>/mounts. -hpa - 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