From: Ian Kent <raven@themaw.net>
To: Al Viro <viro@ZenIV.linux.org.uk>
Cc: Jim Garlick <garlick@llnl.gov>,
linux-fsdevel@vger.kernel.org, Sage Weil <sage@newdream.net>,
"H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [PATCH 1/2] vfs: make real_lookup do dentry revalidation with
Date: Wed, 07 Oct 2009 12:04:48 +0800 [thread overview]
Message-ID: <4ACC1360.9030007@themaw.net> (raw)
In-Reply-To: <4ABB2178.3090500@themaw.net>
Ian Kent wrote:
> Al Viro wrote:
>> On Thu, Sep 24, 2009 at 11:50:55AM +0800, Ian Kent wrote:
>>> Jim Garlick wrote:
>>>> On Thu, Sep 17, 2009 at 06:36:49AM +0800, Ian Kent wrote:
>>>>> So, it's probably time to post my patch series to get some more eyes
>>>>> looking at them. Who on the recipient list of this mail should I include
>>>>> for the post?
>>>> I'm keen to see Sage's patch land in -mm. I'd be happy to help review/test
>>>> your changes if it would help move things along.
>>> Wow, at last some interest.
>>>
>>> I was beginning to think my painstaking effort had been wasted.
>>>
>>> We will need to verify the patch I've used for the VFS locking is
>>> adequate because I had some difficulty working out which of the several
>>> originally posted were the ones needed and at least one didn't even
>>> apply. It will be included in the series I post.
>>>
>>> Since no-one else has replied I'll post the patch series and copy
>>> everyone on the cc list of the original discussion and yourself.
>> It's definitely not wasted. I have a patch series massaging the pathname
>> resolution sitting in the local tree and once I'm done with the misc stuff
>> (tonight, hopefully) it'll be time for that one. I was going to ask you
>> to post once I get to that, since it clearly needs to be integrated.
>> So if you have the patch series against the current mainline, please post
>> it and I'll deal with that.
>
> OK, I'll pull the latest changes into my local tree and check there are
> no surprises, then post the series. Unfortunately, the series is not
> trivial so review will be difficult for those not familiar with the
> issues. But it does need review before going further.
>
> I'm not sure what to do about the autofs module, namely the removal and
> rename of autofs4 to autofs, since that will require a fair amount of
> experimentation to make it, at least as much as is possible, a seamless
> change wrt. to the module usage. OTOH, there aren't many users, if any
> at all, of the autofs module nowadays. Perhaps people with embedded
> devices are still using it, I don't know.
>
> Thoughts?
I still need to deal with the autofs module.
I'm reluctant to remove it and do the rename at the same time the other
changes are going in.
I thought a better idea would be to leave the autofs module in place for
the moment and change the Kconfig help message to describe what is going
to happen and alert users to the fact it won't work and also change all
the defconfig files that select autofs to select autofs4.
Thoughts please?
Ian
next prev parent reply other threads:[~2009-10-07 4:05 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 [this message]
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
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=4ACC1360.9030007@themaw.net \
--to=raven@themaw.net \
--cc=garlick@llnl.gov \
--cc=hpa@zytor.com \
--cc=linux-fsdevel@vger.kernel.org \
--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).