mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Steve French <smfrench@austin.rr.com>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: rddunlap@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: uid of user who mounts
Date: Sat, 31 Jul 2004 10:21:48 -0500	[thread overview]
Message-ID: <1091287308.2337.6.camel@smfhome.smfdom> (raw)
In-Reply-To: <E1BqqGd-0004fX-00@dorka.pomaz.szeredi.hu>

That is an interesting patch. 

I confirmed what Randy had mantioned about the user= entries in mtab
allowing umounts (at least it works that way for a few of the local
filesystems I tried) but did not seem to work so well on other
filesystems - I had odd results on umounting my cifs mounts e.g. - after
adding at mount time "user=someuser" to /etc/mtab (by a minor change to
the mount helper mount.cifs.c, when running mount.cifs suid).  umount of
those mounts failed and has been tricky to debug through a privately
built version of umount via ddd (although it is clearly not making it
down to the cifs filesystem on the user umount so the problem is in libc
or in fs/namespace.c) - so I am tracing through fs/namespace.c now.

On Sat, 2004-07-31 at 04:35, Miklos Szeredi wrote:
> Steve French wrote:
> > 
> > Thanks - I had missed that - and it is a little cleaner to call it
> > "user" than "mount_uid" in the line in /proc/mounts, and there are no
> > existing parms returned that are similar (except "username" which should
> > be easy enough to understand). Interestingly I did not see other
> > filesystems returning that in /proc/mounts (I slightly prefer having it
> > stored in the filesystems kernel code and returned in showopts not just
> > put by userspace in the file mtab) - the only minor annoyance is that /
> > etc/mtab returns the username (rather than the uid).
> 
> I support adding 'user=UID' to the /proc/mounts output.  Actually I
> have an older patch which contains this feature.  This is slightly big
> patch which also deals with completely elliminating the need for a
> suid mount program for some specific filesystems.  See:
> 
> http://marc.theaimsgroup.com/?l=linux-fsdevel&m=108116200509753&w=2
> 
> Miklos


  reply	other threads:[~2004-07-31 15:21 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-31  2:05 Steve French
2004-07-31  2:08 ` Randy.Dunlap
2004-07-31  3:34   ` Steve French
2004-07-31  9:35     ` Miklos Szeredi
2004-07-31 15:21       ` Steve French [this message]
2004-07-31 17:31         ` Miklos Szeredi
2004-07-31 17:49           ` Steve French
2004-07-31 18:12         ` Steve French
2004-07-31 19:11         ` Andries Brouwer
2004-07-31 19:43           ` Miklos Szeredi

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1091287308.2337.6.camel@smfhome.smfdom \
    --to=smfrench@austin.rr.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    --cc=rddunlap@osdl.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®