From: "J. Bruce Fields" <bfields@fieldses.org>
To: "J. Bruce Fields" <bfields@redhat.com>
Cc: Al Viro <viro@ZenIV.linux.org.uk>,
Christoph Hellwig <hch@infradead.org>,
linux-fsdevel@vger.kernel.org, linux-nfs@vger.kernel.org,
sandeen@redhat.com
Subject: Re: [PATCH 2/2] exportfs: fix 32-bit nfsd handling of 64-bit inode numbers
Date: Tue, 8 Oct 2013 17:56:56 -0400 [thread overview]
Message-ID: <20131008215656.GA3456@fieldses.org> (raw)
In-Reply-To: <20131004221522.GD18051@fieldses.org>
On Fri, Oct 04, 2013 at 06:15:22PM -0400, J. Bruce Fields wrote:
> On Fri, Oct 04, 2013 at 06:12:16PM -0400, bfields wrote:
> > On Wed, Oct 02, 2013 at 05:28:14PM -0400, J. Bruce Fields wrote:
> > > @@ -268,6 +268,16 @@ static int get_name(const struct path *path, char *name, struct dentry *child)
> > > if (!dir->i_fop)
> > > goto out;
> > > /*
> > > + * inode->i_ino is unsigned long, kstat->ino is u64, so the
> > > + * former would be insufficient on 32-bit hosts when the
> > > + * filesystem supports 64-bit inode numbers. So we need to
> > > + * actually call ->getattr, not just read i_ino:
> > > + */
> > > + error = vfs_getattr_nosec(path, &stat);
> >
> > Doh, "path" here is for the parent.... The following works better!
>
> By the way, I'm testing this with:
>
> - create a bunch of nested subdirectories, use
> name_to_fhandle_at to get a handle for the bottom directory.
> - echo 2 >/proc/sys/vm/drop_caches
> - open_by_fhandle_at on the filehandle
>
> But this only actually exercises the reconnect path on the first run
> after boot. Is there something obvious I'm missing here?
Looking at the code.... OK, most of the work of drop_caches is done by
shrink_slab_node, which doesn't actually try to free every single thing
that it could free--in particular, it won't try to free anything if it
thinks there are less than shrinker->batch_size (1024 in the
super_block->s_shrink case) objects to free.
So for now I'm just nesting deeper (2048 subdirectories) to get a
reliable way to exercise reconnect_path.
--b.
next prev parent reply other threads:[~2013-10-08 21:57 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-12 16:03 why is i_ino unsigned long, anyway? J. Bruce Fields
2013-09-12 19:33 ` Al Viro
[not found] ` <20130912193328.GP13318-3bDd1+5oDREiFSDQTTA3OLVCufUGDwFn@public.gmane.org>
2013-09-29 11:54 ` Christoph Hellwig
[not found] ` <20130929115454.GA3953-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
2013-10-02 14:25 ` J. Bruce Fields
[not found] ` <20131002142527.GD14808-uC3wQj2KruNg9hUCZPvPmw@public.gmane.org>
2013-10-02 15:43 ` J. Bruce Fields
[not found] ` <20131002154320.GE14808-uC3wQj2KruNg9hUCZPvPmw@public.gmane.org>
2013-10-02 16:04 ` Christoph Hellwig
2013-10-02 18:14 ` J. Bruce Fields
2013-10-02 16:05 ` Christoph Hellwig
[not found] ` <20131002160527.GB23875-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
2013-10-02 17:53 ` J. Bruce Fields
[not found] ` <20131002175328.GF14808-uC3wQj2KruNg9hUCZPvPmw@public.gmane.org>
2013-10-02 17:57 ` Christoph Hellwig
2013-10-02 21:07 ` J. Bruce Fields
[not found] ` <20131002210736.GA20598-uC3wQj2KruNg9hUCZPvPmw@public.gmane.org>
2013-10-02 21:28 ` [PATCH 1/2] vfs: split out vfs_getattr_nosec J. Bruce Fields
2013-10-02 21:28 ` [PATCH 2/2] exportfs: fix 32-bit nfsd handling of 64-bit inode numbers J. Bruce Fields
[not found] ` <1380749295-20854-2-git-send-email-bfields-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2013-10-04 22:12 ` J. Bruce Fields
[not found] ` <20131004221216.GC18051-uC3wQj2KruNg9hUCZPvPmw@public.gmane.org>
2013-10-04 22:15 ` J. Bruce Fields
2013-10-08 21:56 ` J. Bruce Fields [this message]
2013-10-09 0:16 ` Dave Chinner
2013-10-09 14:53 ` J. Bruce Fields
2013-10-10 22:28 ` Dave Chinner
2013-10-11 21:53 ` J. Bruce Fields
2013-10-13 22:52 ` Dave Chinner
2013-10-02 18:47 ` why is i_ino unsigned long, anyway? Sage Weil
[not found] ` <alpine.DEB.2.00.1310021130280.7765-vIokxiIdD2AQNTJnQDzGJqxOck334EZe@public.gmane.org>
2013-10-02 19:00 ` J. Bruce Fields
[not found] ` <20131002190034.GH14808-uC3wQj2KruNg9hUCZPvPmw@public.gmane.org>
2013-10-02 19:04 ` Sage Weil
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=20131008215656.GA3456@fieldses.org \
--to=bfields@fieldses.org \
--cc=bfields@redhat.com \
--cc=hch@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=sandeen@redhat.com \
--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;
as well as URLs for NNTP newsgroup(s).