linux-kernel - Re: [patch 4/6] vfs: mountinfo show dominating group id

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: <E1Jbx0r-00027l-0q@pomaz-ex.szeredi.hu>
Date:	Wed, 19 Mar 2008 13:03:21 +0100
From:	Miklos Szeredi <miklos@...redi.hu>
To:	viro@...IV.linux.org.uk
CC:	miklos@...redi.hu, akpm@...ux-foundation.org, linuxram@...ibm.com,
	linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [patch 4/6] vfs: mountinfo show dominating group id

> > From: Miklos Szeredi <mszeredi@...e.cz>
> > 
> > Show peer group ID of nearest dominating group that has intersection
> > with the mount's namespace.
> 
> There's an obvious problem here: ->show_options() can spew _anything_,
> including a string that ends on " shared:42".

Yeah, even though I'd call that very broken, I wouldn't like to go
auditing filesystems for such breakage.

>  Makes reliable parsing of
> the damn thing in userland impossible.  IOW, fs options should go _last_
> and they should follow an unconditionally present field.

But then we lose the ability to later extend the format by adding
fields at the end.  Which is one of the things that would be nice to
have, in contrast to /proc/mounts, which we are so afraid to touch now.

So maybe some alternative, multi line format would be better?

MountID: 99
ParentID: 88
DevID: 0:34
Type: foofs
Source: /dev/foo
Root: /
MountPoint: /mnt/foo
MountOpts: rw,noatime
Opts: rw,errors=continue
Propagation: shared:42

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