From: NeilBrown <neilb@suse.de>
To: Ian Kent <raven@themaw.net>
Cc: autofs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/5] RCU-walk support for autofs
Date: Tue, 19 Aug 2014 21:16:54 +1000 [thread overview]
Message-ID: <20140819211654.5ec3853a@notabene.brown> (raw)
In-Reply-To: <1408442547.11314.9.camel@perseus.themaw.net>
[-- Attachment #1: Type: text/plain, Size: 2182 bytes --]
On Tue, 19 Aug 2014 18:02:27 +0800 Ian Kent <raven@themaw.net> wrote:
> On Mon, 2014-08-18 at 16:25 +0800, Ian Kent wrote:
> > On Mon, 2014-08-18 at 16:33 +1000, NeilBrown wrote:
> > > Hi Ian,
> > > Have you had a chance to run your tests in these patches yet?
> > > I've done what testing I can think of and cannot fault them.
> >
> > I haven't, I've been plagued with illness so I'm not getting nearly
> > enough done. I'll try to put a kernel together and run the test in the
> > next week or so.
>
> Just to let you know that I managed to spend some time on this. I built
> a kernel (3.17.0-rc1) with the series and ran a couple of tests.
>
> I'm not certain that the patches I used are identical to your posting, I
> saw one difference, after the fact, that shouldn't matter, I'll have to
> check that.
>
> It isn't possible to test expire to mount races because the mounts in
> the tree never expire.
>
> At first I thought it was because so many processes were accessing the
> tree all the time but manually constructing the maps and mounting the
> mounts shows that nothing ever expires, at least for this tree.
>
> However, issuing a shut down does expire all the mounts and shuts down
> autofs cleanly.
>
> So there is something not quite right with the expire check or my
> patches have mistakes.
Ahh.. I bet I know what it is.
autofs4_can_expire() isn't idempotent.
Because we call should_expire twice, autofs4_can_expire() is called twice and
the second time it failed because the first time it resets ->last_used.
diff --git a/fs/autofs4/expire.c b/fs/autofs4/expire.c
index eb4b770a4bf6..80133a9d9427 100644
--- a/fs/autofs4/expire.c
+++ b/fs/autofs4/expire.c
@@ -26,6 +26,9 @@ static inline int autofs4_can_expire(struct dentry *dentry,
if (ino == NULL)
return 0;
+ if (ino->flags & AUTOFS_INF_NO_RCU)
+ /* Already performed this test */
+ return 1;
if (!do_now) {
/* Too young to die */
if (!timeout || time_after(ino->last_used + timeout, now))
might fix it, but might be a hack.
(tests.... yep, that seems to fix it).
I'll think some more tomorrow.
Thanks,
NeilBrown
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2014-08-19 11:17 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-18 6:33 [PATCH 0/5] RCU-walk support for autofs NeilBrown
2014-08-18 6:33 ` [PATCH 1/5] autofs4: allow RCU-walk to walk through autofs4 NeilBrown
2014-08-18 6:33 ` [PATCH 4/5] autofs4: d_manage() should return -EISDIR when appropriate in rcu-walk mode NeilBrown
2014-08-18 6:33 ` [PATCH 2/5] autofs4: factor should_expire() out of autofs4_expire_indirect NeilBrown
2014-08-18 6:33 ` [PATCH 3/5] autofs4: avoid taking fs_lock during rcu-walk NeilBrown
2014-08-18 6:33 ` [PATCH 5/5] autofs: the documentation I wanted to read NeilBrown
2014-08-18 10:13 ` Ian Kent
2014-08-19 7:00 ` NeilBrown
2014-08-18 8:25 ` [PATCH 0/5] RCU-walk support for autofs Ian Kent
2014-08-19 10:02 ` Ian Kent
2014-08-19 11:16 ` NeilBrown [this message]
2014-08-19 12:30 ` Ian Kent
2014-08-19 12:36 ` Ian Kent
2014-08-20 3:13 ` NeilBrown
2014-08-20 3:42 ` Ian Kent
2014-08-20 3:50 ` Ian Kent
2014-08-20 9:52 ` Ian Kent
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=20140819211654.5ec3853a@notabene.brown \
--to=neilb@suse.de \
--cc=autofs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=raven@themaw.net \
/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