From: Ian Kent <raven@themaw.net>
To: Sage Weil <sage@newdream.net>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: Al Viro <viro@ZenIV.linux.org.uk>,
Christoph Hellwig <hch@infradead.org>,
Andreas Dilger <adilger@sun.com>,
Yehuda Saheh <yehuda@newdream.net>,
Jim Garlick <garlick@llnl.gov>
Subject: [RFC PATCH 0/3] autofs - series to replace autofs with autofs4
Date: Thu, 26 Nov 2009 11:21:47 +0800 [thread overview]
Message-ID: <20091126030623.5691.33759.stgit@zeus.themaw.net> (raw)
Due to planned changes to locking for the path walking the autofs
module could easily deadlock during mount request callback. Since
the autofs4 module provides the needed support and a patch series
to overcome the locking change has been done, rather than attempt
to fix autofs I propose that the autofs module be replaced by the
autofs4 module.
To try and give people some warning before actually removing the
autofs4 directory I've left that in place, updated the Kconfig
help text to warn of the impending removal, and provided a make
that builds into the autofs4 directory from the updated autofs
directory source. The net result is that fs/autofs/autofs.ko and
fs/autofs4/autofs4.ko will be built from the same source.
Also, the defconfig configurations have not yet been changed but
that can be done upon actual removal.
Comments on this appraoch and the patch series are welcome.
---
Ian Kent (3):
autofs - use consistent function naming
autofs - rename autofs4 module to autofs
autofs4 - coding style fixes
fs/autofs/Kconfig | 12
fs/autofs/Makefile | 2
fs/autofs/autofs_i.h | 317 +++++++++---
fs/autofs/dev-ioctl.c | 766 +++++++++++++++++++++++++++++
fs/autofs/dirhash.c | 250 ---------
fs/autofs/expire.c | 531 ++++++++++++++++++++
fs/autofs/init.c | 30 -
fs/autofs/inode.c | 406 +++++++++++----
fs/autofs/root.c | 1268 ++++++++++++++++++++++++++++++++++--------------
fs/autofs/symlink.c | 10
fs/autofs/waitq.c | 474 +++++++++++++++---
fs/autofs4/Kconfig | 10
fs/autofs4/Makefile | 10
fs/autofs4/autofs_i.h | 304 ------------
fs/autofs4/dev-ioctl.c | 765 -----------------------------
fs/autofs4/expire.c | 530 --------------------
fs/autofs4/init.c | 51 --
fs/autofs4/inode.c | 473 ------------------
fs/autofs4/root.c | 1109 ------------------------------------------
fs/autofs4/symlink.c | 25 -
fs/autofs4/waitq.c | 524 --------------------
21 files changed, 3157 insertions(+), 4710 deletions(-)
create mode 100644 fs/autofs/dev-ioctl.c
delete mode 100644 fs/autofs/dirhash.c
create mode 100644 fs/autofs/expire.c
delete mode 100644 fs/autofs4/autofs_i.h
delete mode 100644 fs/autofs4/dev-ioctl.c
delete mode 100644 fs/autofs4/expire.c
delete mode 100644 fs/autofs4/init.c
delete mode 100644 fs/autofs4/inode.c
delete mode 100644 fs/autofs4/root.c
delete mode 100644 fs/autofs4/symlink.c
delete mode 100644 fs/autofs4/waitq.c
--
Ian
next reply other threads:[~2009-11-26 3:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-26 3:21 Ian Kent [this message]
2009-11-26 3:21 ` [RFC PATCH 1/3] autofs4 - coding style fixes Ian Kent
2009-11-26 3:22 ` [RFC PATCH 2/3] autofs - rename autofs4 module to autofs Ian Kent
2009-11-26 3:22 ` [RFC PATCH 3/3] autofs - use consistent function naming 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=20091126030623.5691.33759.stgit@zeus.themaw.net \
--to=raven@themaw.net \
--cc=adilger@sun.com \
--cc=garlick@llnl.gov \
--cc=hch@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sage@newdream.net \
--cc=viro@ZenIV.linux.org.uk \
--cc=yehuda@newdream.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
all inboxes | Powered by JetHome®