From: Christoph Hellwig <hch@infradead.org>
To: "Bodo Eggert <harvested.in.lkml@posting.7eggert.dyndns.org>"
<7eggert@gmx.de>
Cc: Steve French <smfrench@austin.rr.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] cifs: handle termination of cifs oplockd kernel thread
Date: Sat, 30 Apr 2005 08:32:38 +0100 [thread overview]
Message-ID: <20050430073238.GA22673@infradead.org> (raw)
In-Reply-To: <E1DRekV-0001RN-VQ@be1.7eggert.dyndns.org>
On Sat, Apr 30, 2005 at 01:18:19AM +0200, Bodo Eggert <harvested.in.lkml@posting.7eggert.dyndns.org> wrote:
> 4) Turn umounting own mounts into a non-privileged operation.
>
> As (AFAI see) the only thing that needs suid privileges is the umount
> operation, and it is granted if the user mounted it himself, you can as
> well do this simple check in the kernel.
Except that we don't have the concept of a mount owner at the VFS level
right now, because everyone is adding stupid suid wrapper hacks instead
of trying to fix the problems for real.
next prev parent reply other threads:[~2005-04-30 7:32 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3YLdQ-4vS-15@gated-at.bofh.it>
2005-04-29 23:18 ` [PATCH] cifs: handle termination of cifs oplockd kernel thread Bodo Eggert <harvested.in.lkml@posting.7eggert.dyndns.org>
2005-04-30 7:32 ` Christoph Hellwig [this message]
2005-04-30 8:14 ` Miklos Szeredi
2005-04-30 8:29 ` Christoph Hellwig
2005-04-30 9:22 ` Miklos Szeredi
2005-04-30 10:57 ` Miklos Szeredi
2005-04-30 13:28 ` Steve French
2005-04-30 14:53 ` J. Bruce Fields
2005-04-30 14:50 ` Steve French
2005-04-30 17:23 ` Miklos Szeredi
2005-04-30 16:16 ` Miklos Szeredi
2005-04-30 15:27 ` Steve French
2005-05-01 0:10 ` Bodo Eggert
2005-05-11 8:59 ` Christoph Hellwig
2005-04-30 12:52 ` Steve French
2005-04-29 21:09 Steve French
2005-04-29 21:31 ` Christoph Hellwig
2005-04-29 22:20 ` Steve French
2005-05-11 8:56 ` Christoph Hellwig
2005-05-11 18:19 ` Steve French
2005-05-16 9:34 ` Christoph Hellwig
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=20050430073238.GA22673@infradead.org \
--to=hch@infradead.org \
--cc=7eggert@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=smfrench@austin.rr.com \
/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