public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Steve French <smfrench@austin.rr.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] cifs: handle termination of cifs oplockd kernel thread
Date: Mon, 16 May 2005 10:34:08 +0100	[thread overview]
Message-ID: <20050516093408.GA20696@infradead.org> (raw)
In-Reply-To: <42824CA7.9040201@austin.rr.com>

On Wed, May 11, 2005 at 01:19:19PM -0500, Steve French wrote:
> OK - why don't we just add this (ie the ioctl removal) to the patch
> 
> [PATCH] unprivileged mount/umount
> 
> of Miklos et al, since that removes the need to modify showmounts (and 
> avoids any name collision/confusion
> with the existing meaning of the mount option "uid" ie as the default 
> uid to use for files on the system when
> mounting to servers which can not return inode owners as uids).

I think that would be best.  It still needs a little work first.

> On another topic relating to ioctls, various people have suggested 
> adding an ioctl to add a table to optionally map file owner (uid / gid 
> mapping tables) on remote filesystems. Although this is easy enough to 
> do for the case of CIFS, this seems like a function (loading the table) 
> that could be done via /proc or perhaps even sysfs. Is there are 
> precedent for doing this on Linux?

I don't think that mapping should happen in kernelspace.  It would
be nice if you could share that with nfs, maybe even generalizing the
nfsv4 one.


  reply	other threads:[~2005-05-16  9:34 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-29 21:09 [PATCH] cifs: handle termination of cifs oplockd kernel thread 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 [this message]
     [not found] <3YLdQ-4vS-15@gated-at.bofh.it>
2005-04-29 23:18 ` Bodo Eggert <harvested.in.lkml@posting.7eggert.dyndns.org>
2005-04-30  7:32   ` Christoph Hellwig
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

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=20050516093408.GA20696@infradead.org \
    --to=hch@infradead.org \
    --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