linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: Jim Rees <rees@umich.edu>
Cc: Sven Geggus <lists@fuchsschwanzdomain.de>, linux-nfs@vger.kernel.org
Subject: Re: NFS4: ssh + unlink(~/.Xauthority) delays
Date: Tue, 21 Aug 2012 16:59:41 -0400	[thread overview]
Message-ID: <20120821205941.GA18637@fieldses.org> (raw)
In-Reply-To: <20120821184230.GA13357@umich.edu>

On Tue, Aug 21, 2012 at 02:42:30PM -0400, Jim Rees wrote:
> Malahal Naineni wrote:
> 
>   NFS3 doesn't have delegations and this file placement should not be an
>   issue in NFSv4 either if it is working correctly!
> 
> Xauthority doesn't belong in $HOME, it belongs on the local disk.  That has
> nothing to do with NFS v3/v4.  It has to do with limiting distribution and
> exposure of sensitive information.

Yah.  Unlinking a file shouldn't take a minute, though, so we do have a
bug, however it was found.  Let me know if the patch I referred to fixes
it.

--b.

      reply	other threads:[~2012-08-21 20:59 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-21  8:25 NFS4: ssh + unlink(~/.Xauthority) delays Sven Geggus
2012-08-21  9:19 ` NFS4ERR_DELAY (was: NFS4: ssh + unlink(~/.Xauthority) delays) Sven Geggus
2012-08-21 10:41   ` Jeff Layton
2012-08-21 12:52     ` NFS4ERR_DELAY Sven Geggus
2012-08-21 13:07       ` NFS4ERR_DELAY Jeff Layton
2012-08-21 17:47         ` NFS4ERR_DELAY J. Bruce Fields
2012-08-22  8:33           ` NFS4ERR_DELAY Sven Geggus
2012-08-21 12:59 ` NFS4: ssh + unlink(~/.Xauthority) delays Jim Rees
2012-08-21 16:04   ` Sven Geggus
2012-08-21 17:07     ` Jim Rees
2012-08-21 18:03       ` Malahal Naineni
2012-08-21 18:42         ` Jim Rees
2012-08-21 20:59           ` J. Bruce Fields [this message]

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=20120821205941.GA18637@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=lists@fuchsschwanzdomain.de \
    --cc=rees@umich.edu \
    /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).