From: Ian Kent <raven@themaw.net>
To: NeilBrown <neilb@suse.de>
Cc: autofs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/5] RCU-walk support for autofs
Date: Mon, 18 Aug 2014 16:25:40 +0800 [thread overview]
Message-ID: <1408350340.2533.3.camel@perseus.fritz.box> (raw)
In-Reply-To: <20140818062844.9860.43007.stgit@notabene.brown>
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.
>
> This set is against 3.17-rc1 and make use of the new -EISDIR handling
> for d_manage() and assumes the other patches which already went in
> through Andrew Morton.
>
> I've added a section to autofs4.txt about mount namespaces, but it is
> otherwise unchanged.
>
> If I could get an {Acked,Reviewed,Tested}-By in the next few weeks so
> I can send them on to Andrew I would really appreciate it.
>
> Thanks,
> NeilBrown
>
>
>
> ---
>
> NeilBrown (5):
> autofs4: allow RCU-walk to walk through autofs4.
> autofs4: factor should_expire() out of autofs4_expire_indirect.
> autofs4: avoid taking fs_lock during rcu-walk
> autofs4: d_manage() should return -EISDIR when appropriate in rcu-walk mode.
> autofs: the documentation I wanted to read
>
>
> Documentation/filesystems/autofs4.txt | 520 +++++++++++++++++++++++++++++++++
> fs/autofs4/autofs_i.h | 6
> fs/autofs4/dev-ioctl.c | 2
> fs/autofs4/expire.c | 200 ++++++++-----
> fs/autofs4/root.c | 62 +++-
> 5 files changed, 694 insertions(+), 96 deletions(-)
> create mode 100644 Documentation/filesystems/autofs4.txt
>
next prev parent reply other threads:[~2014-08-18 8:25 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 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 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 4/5] autofs4: d_manage() should return -EISDIR when appropriate in rcu-walk mode NeilBrown
2014-08-18 8:25 ` Ian Kent [this message]
2014-08-19 10:02 ` [PATCH 0/5] RCU-walk support for autofs Ian Kent
2014-08-19 11:16 ` NeilBrown
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=1408350340.2533.3.camel@perseus.fritz.box \
--to=raven@themaw.net \
--cc=autofs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@suse.de \
/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.