From: Christoph Hellwig <hch@infradead.org>
To: Ian Kent <raven@themaw.net>
Cc: Jeff Moyer <jmoyer@redhat.com>, Al Viro <viro@ZenIV.linux.org.uk>,
Jim Garlick <garlick@llnl.gov>,
linux-fsdevel@vger.kernel.org, Sage Weil <sage@newdream.net>,
"H. Peter Anvin" <hpa@zytor.com>,
Christoph Hellwig <hch@infradead.org>
Subject: Re: [PATCH 1/2] vfs: make real_lookup do dentry revalidation with
Date: Sun, 25 Oct 2009 03:45:01 -0400 [thread overview]
Message-ID: <20091025074501.GB9482@infradead.org> (raw)
In-Reply-To: <4AD538A4.9090609@themaw.net>
On Wed, Oct 14, 2009 at 10:34:12AM +0800, Ian Kent wrote:
> Some time ago Christoph suggested registering both autofs and autofs4
> but I'm not sure about that since both modules have always only
> registered autofs as the file system name.
Oops, I didn't notice that.
> We can add a MODULE_ALIAS() to the module source but that doesn't
> completely work, I think because the user space tools then don't get the
> directory right. Changing the user space configuration is also
> problematic because booting from a kernel with and without would require
> a configuration change every time.
>
> The obvious simple solution would be to use symlinks to make the
> directory and module appear to be present, set about a process of user
> awareness and remove them after some pre-defined number of subsequent
> releases but I'm not sure how that approach would be received? We could
> even write a module stub that issues a warning message to syslog and
> then loads the autofs module but I haven't tried that yet.
>
> Please, folks, some suggestions.
Just build two modules using the same source code? That quite ugly, but
if the userspace is really that messed up I can't think of any better
idea.
next prev parent reply other threads:[~2009-10-25 7:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-23 23:28 [PATCH 1/2] vfs: make real_lookup do dentry revalidation with Jim Garlick
2009-09-24 3:50 ` Ian Kent
2009-09-24 7:00 ` Al Viro
2009-09-24 7:36 ` Ian Kent
2009-10-07 4:04 ` Ian Kent
2009-10-14 1:12 ` Jeff Moyer
2009-10-14 2:34 ` Ian Kent
2009-10-14 2:57 ` Ian Kent
2009-10-14 11:47 ` Jeff Moyer
2009-10-25 7:45 ` Christoph Hellwig [this message]
2009-10-25 23:33 ` 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=20091025074501.GB9482@infradead.org \
--to=hch@infradead.org \
--cc=garlick@llnl.gov \
--cc=hpa@zytor.com \
--cc=jmoyer@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=raven@themaw.net \
--cc=sage@newdream.net \
--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).