linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: Christoph Hellwig <hch@lst.de>,
	akpm@osdl.org, neilb@cse.unsw.edu.au, andros@citi.umich.edu,
	linux-fsdevel@vger.kernel.org
Subject: Re: NFS4 crack
Date: Mon, 19 Sep 2005 15:39:21 +0200	[thread overview]
Message-ID: <20050919133921.GA12208@lst.de> (raw)
In-Reply-To: <20050919133528.GA20732@fieldses.org>

On Mon, Sep 19, 2005 at 09:35:28AM -0400, J. Bruce Fields wrote:
> On Mon, Sep 19, 2005 at 12:35:47PM +0200, Christoph Hellwig wrote:
> > Namespaces issues above was meant as kernel can't assume namespace at
> > all, not even thinking about multiple namespaces which makes it even
> > more wrong.  Who sais I allow the kernel to mess with
> > /var/lib/nfs/v4recover?
> 
> It's run-time configurable if you don't like the default.
> 
> > Who tells any userspace process is even in the same namespace as the
> > nfs threads to create the directories?
> 
> No userspace process is likely to care, except maybe for debugging
> purposes.  This isn't a userspace<->kernel interface, it's just a way to
> store some information on disk so nfsd can find it again on next boot.

Again,

FILENAMES ARE POLICY AND HAVE NO BUSINESS IN THE KERNEL

if that wasn't clear enough.  You can't contiune enumerating the special
cases in that i could actually work somehow, but that doesn't make the
code any better.  We have a strong policy to not have hardcoded
filenames in the kernel (although a few week abstractions where we
pass something very similar to a filename up to userspace to act on it),
and we're not going to make an exception for NFSv4.  Especially as this
code would be much simpler in userspace as already mentioned.  Directory
handling is something that can't be done sanely in kernelspace.


  reply	other threads:[~2005-09-19 13:39 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-18 10:21 NFS4 crack Christoph Hellwig
2005-09-18 14:36 ` J. Bruce Fields
2005-09-19 10:35   ` Christoph Hellwig
2005-09-19 13:04     ` Anton Altaparmakov
2005-09-19 13:35     ` J. Bruce Fields
2005-09-19 13:39       ` Christoph Hellwig [this message]
2005-09-19 14:07         ` J. Bruce Fields
2005-09-19 14:11           ` Christoph Hellwig
2005-09-19 17:13         ` Bryan Henderson
2005-09-19 17:16           ` Randy.Dunlap
2005-09-19 21:57             ` Bryan Henderson
2005-09-19 22:11               ` Randy.Dunlap
2005-09-20  0:17                 ` Bryan Henderson
2005-09-19 18:02           ` Christoph Hellwig
2005-09-19 18:53             ` William A.(Andy) Adamson
2005-09-19 18:59               ` Christoph Hellwig
2005-09-19 22:04               ` Bryan Henderson
2005-09-19 19:01             ` J. Bruce Fields
2005-09-19 19:05               ` Christoph Hellwig
2005-09-19 20:31     ` J. Bruce Fields
2005-09-20 12:49       ` Greg KH
2005-09-20 15:10         ` William A.(Andy) Adamson
2005-09-20 18:37 ` Neil Brown
2005-09-21  7:44   ` Andrew Morton
2005-09-22 20:58     ` William A.(Andy) Adamson
2005-09-21 13:41   ` Trond Myklebust
2005-09-21 14:40   ` J. Bruce Fields
2005-09-22 16:28   ` Bryan Henderson
2005-09-22 16:52     ` Trond Myklebust
2005-09-22 17:38       ` Peter Staubach
2005-09-22 17:52         ` Trond Myklebust
2005-09-22 18:07           ` Peter Staubach
2005-09-22 21:08             ` Bryan Henderson
2005-09-23 12:17               ` Peter Staubach
2005-09-23 20:50                 ` Bryan Henderson
2005-09-23 21:02                   ` NFS4 crack\ Al Viro
2005-09-26 16:29                     ` Bryan Henderson
2005-09-26 17:13                       ` Peter Staubach
2005-09-22 21:48             ` NFS4 crack Nicholas Miell
2005-09-22 22:50             ` Greg Banks
2005-09-22 21:19         ` Bryan Henderson

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=20050919133921.GA12208@lst.de \
    --to=hch@lst.de \
    --cc=akpm@osdl.org \
    --cc=andros@citi.umich.edu \
    --cc=bfields@fieldses.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=neilb@cse.unsw.edu.au \
    /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;
as well as URLs for NNTP newsgroup(s).