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]
Date:	Tue, 24 Jul 2007 07:11:19 +0200
From:	Miklos Szeredi <miklos@...redi.hu>
To:	tytso@....edu
CC:	akpm@...ux-foundation.org, miklos@...redi.hu,
	linux-ext4@...r.kernel.org
Subject: Re: [PATCH 1/3] ext2: show all mount options

> The idea is to allow /proc/mounts to display all of the mount options
> that were used to mount a particular filesystem.  This is useful if
> you want /proc/mounts to replace /etc/mtab.
> 
> I keep thinking that this is really the wrong approach, though, since
> it means adding a lot of coding to every single filesystem to
> reconstruct the mount options, and in some cases it will still never
> be enough to reconstruct exactly what was in /etc/mtab.  (For example,
> the fully qualified domain named passed into some remote filesystem.)
> 
> It seems to me the right answer would be to enhance the mount(2)
> system call with a new mount operation which would allow the user
> space mount command can stash exactly the options used to mount the
> filesystem.

Well, that would be good for emulating /etc/mtab.  But the problem is
that that's wrong a lot of times.  For example in ext* "mount
-oremount,opt" doesn't reset all options, it just changes "opt".  And
this is different from fs to fs, so there's no easy way to handle it
from generic code.

I think it shouln't be hard to keep the shown mount options in sync
with the parsed options.  The problem is just that people have been
lazy to do that, because /etc/mtab was good enough.

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ