Linux NFS development
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: Frank Filz <ffilzlnx@us.ibm.com>
Cc: NFS V4 Mailing List <nfsv4@linux-nfs.org>,
	NFS List <linux-nfs@vger.kernel.org>, Neil Brown <neilb@suse.de>,
	ffilz@us.ibm.com
Subject: Re: [PATCH] nfsd: Fix compatibility issue with AIX client using READDIR when directory contains a sub-mounted filesystem
Date: Tue, 27 Nov 2007 16:09:10 -0500	[thread overview]
Message-ID: <20071127210910.GF27242@fieldses.org> (raw)
In-Reply-To: <1196192046.3265.30.camel@dyn9047022153>

On Tue, Nov 27, 2007 at 11:34:05AM -0800, Frank Filz wrote:
> On Mon, 2007-11-26 at 22:28 +0000, J. Bruce Fields wrote:
> > On Mon, Nov 26, 2007 at 01:19:11PM -0800, Frank Filz wrote:
> > OK, thanks!  My only superficial complaint--I find the
> > OBEY_CROSSMNT/IGNORE_CROSSMNT defines to be minor overkill.
> > 
> > If you want to stick with them, then you should probably use a
> > comparison to IGNORE_CROSSMNT here instead of assuming which is zero:
> > 
> > > +                if (!ignore_crossmnt &&
> > > +		    exp->ex_mnt->mnt_root->d_inode == dentry->d_inode) {
> > >  			err = vfs_getattr(exp->ex_mnt->mnt_parent,
> > >  				exp->ex_mnt->mnt_mountpoint, &stat);
> > 
> > But I think it'd be simplest just to use 0 and 1 directly instead of the
> > defines.
> 
> Ok, here's an updated patch removing the #defines. I did also explicitly
> test ignore_crossmnt for 0 instead of implicitly testing.

OK, in all I think the new version's a little more straightforward.
Thanks!  Applied and pushed out to

	git://linux-nfs.org/~bfields nfs-server-stable

and should go in 2.6.25.

--b.

      reply	other threads:[~2007-11-27 21:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-26 21:19 [PATCH] nfsd: Fix compatibility issue with AIX client using READDIR when directory contains a sub-mounted filesystem Frank Filz
2007-11-26 22:28 ` J. Bruce Fields
2007-11-27 19:34   ` Frank Filz
2007-11-27 21:09     ` 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=20071127210910.GF27242@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=ffilz@us.ibm.com \
    --cc=ffilzlnx@us.ibm.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=neilb@suse.de \
    --cc=nfsv4@linux-nfs.org \
    /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