From: "J. Bruce Fields" <bfields@fieldses.org>
To: Al Viro <viro@ZenIV.linux.org.uk>
Cc: Al Viro <viro-rfM+Q5joDG/XmaaqVzeoHQ@public.gmane.org>,
linux-nfs@vger.kernel.org
Subject: Re: [patches] nfsd-affecting part of vfs queue
Date: Wed, 22 Apr 2009 21:59:16 -0400 [thread overview]
Message-ID: <20090423015916.GA16694@fieldses.org> (raw)
In-Reply-To: <20090422230039.GQ8633@ZenIV.linux.org.uk>
On Thu, Apr 23, 2009 at 12:00:39AM +0100, Al Viro wrote:
> On Wed, Apr 22, 2009 at 05:34:15PM -0400, J. Bruce Fields wrote:
> > On Tue, Apr 21, 2009 at 09:43:41PM +0000, Al Viro wrote:
> > >
> > > Fix for out-order dput() vs. mntput() (in nfsd_cross_mnt()) plus
> > > several "switch to passing struct path *" ones. Comments would
> > > be welcome...
> > >
> > > Entire queue is on git.kernel.org/pub/scm/linux/kernel/git/viro/vfs-2.6.git/
> > > in "untested".
> >
> > I haven't tested them, but otherwise they look like fine. Shall queue
> > them in the nfsd tree?
>
> Several patches later in VFS queue depend on those, so I'm definitely keeping
> them in there; might make sense to duplicate in nfsd tree as well to avoid
> inter-tree dependencies. Hell knows, git will cope with that just fine,
> so linux-next will be OK with that, but -mm used to have problems with such
> things, IIRC.
OK. I'll just ignore them unless it becomes a problem.
I did boot your tree above (c65d9c93...) and run a test or two without
seeing any obvious problem. Feel free to add an
Acked-by: J. Bruce Fields <bfields@citi.umich.edu>
--b.
prev parent reply other threads:[~2009-04-23 1:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-21 21:43 [patches] nfsd-affecting part of vfs queue Al Viro
2009-04-22 21:34 ` J. Bruce Fields
2009-04-22 23:00 ` Al Viro
2009-04-23 1: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=20090423015916.GA16694@fieldses.org \
--to=bfields@fieldses.org \
--cc=linux-nfs@vger.kernel.org \
--cc=viro-rfM+Q5joDG/XmaaqVzeoHQ@public.gmane.org \
--cc=viro@ZenIV.linux.org.uk \
/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