All of lore.kernel.org
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: Christoph Hellwig <hch@infradead.org>
Cc: Stanislav Kinsbursky <skinsbursky@parallels.com>,
	"Trond.Myklebust@netapp.com" <Trond.Myklebust@netapp.com>,
	"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"devel@openvz.org" <devel@openvz.org>,
	"Eric W. Biederman" <ebiederm@xmission.com>
Subject: Re: [PATCH v3] SUNRPC: set desired file system root before connecting local transports
Date: Tue, 6 Nov 2012 08:36:05 -0500	[thread overview]
Message-ID: <20121106133605.GD6718@fieldses.org> (raw)
In-Reply-To: <20121106131018.GA12211@infradead.org>

On Tue, Nov 06, 2012 at 08:10:18AM -0500, Christoph Hellwig wrote:
> On Tue, Nov 06, 2012 at 08:07:06AM -0500, J. Bruce Fields wrote:
> > So you're worried that a bug in the nfs code could modify the root and
> > then not restore it?
> 
> At least the link you pointed to earlier never sets it back.

This? http://thread.gmane.org/gmane.linux.kernel/1259986/focus=47687

	+	get_fs_root(current->fs, &root);
	+	set_fs_root(current->fs, &transport->root);
	+
	 	status = xs_local_finish_connecting(xprt, sock);
	+
	+	set_fs_root(current->fs, &root);
	+	path_put(&root);

> Instead
> of messing with it I'd rather have the sunrpc code use vfs_path_lookup
> and not care about current->fs->root at all.

The annoyance is that the lookup happens somewhere lower down in the
networking code (net/unix/af_unix.c:unix_find_other, I think).  So we'd
need some new (internal) API.  We'd likely be the only user of that new
API.

--b.

  reply	other threads:[~2012-11-06 13:36 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-08 10:56 [PATCH v3] SUNRPC: set desired file system root before connecting local transports Stanislav Kinsbursky
2012-10-09 19:35 ` J. Bruce Fields
2012-10-09 19:49   ` Myklebust, Trond
2012-10-09 19:49     ` Myklebust, Trond
2012-10-09 20:20     ` Eric W. Biederman
2012-10-09 22:31       ` J. Bruce Fields
2012-10-09 22:47         ` Eric W. Biederman
2012-10-10  1:23           ` J. Bruce Fields
2012-10-10 10:32             ` Stanislav Kinsbursky
2012-10-26 17:52               ` J. Bruce Fields
2012-10-10  2:00           ` Eric W. Biederman
2012-10-10  5:09             ` Stanislav Kinsbursky
2012-10-10  5:03           ` Stanislav Kinsbursky
2012-11-06 10:14   ` Stanislav Kinsbursky
2012-11-06 12:06     ` J. Bruce Fields
2012-11-06 12:11       ` Stanislav Kinsbursky
2012-11-06 13:05         ` J. Bruce Fields
2012-11-06 12:40       ` Christoph Hellwig
2012-11-06 13:07         ` J. Bruce Fields
2012-11-06 13:10           ` Christoph Hellwig
2012-11-06 13:36             ` J. Bruce Fields [this message]
2012-11-07 18:33               ` J. Bruce Fields
2012-11-12  8:37                 ` Stanislav Kinsbursky
2012-11-14 21:01                   ` J. Bruce Fields
2012-11-14 21:36                     ` Myklebust, Trond
2012-11-14 21:36                       ` Myklebust, Trond
2012-11-14 21:42                       ` J. Bruce Fields
2012-11-14 21:51                         ` Myklebust, Trond
2012-11-14 21:51                           ` Myklebust, Trond
2012-11-14 21:54                           ` J. Bruce Fields
2012-11-15  6:14                             ` Eric W. Biederman
2012-11-15 13:34                               ` Myklebust, Trond
2012-11-15 13:34                                 ` Myklebust, Trond
2012-11-15 18:58                                 ` J. Bruce Fields
2012-11-15  8:35                     ` Stanislav Kinsbursky

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=20121106133605.GD6718@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=Trond.Myklebust@netapp.com \
    --cc=devel@openvz.org \
    --cc=ebiederm@xmission.com \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=skinsbursky@parallels.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.