From: Michael Tokarev <mjt@tls.msk.ru>
To: Ian Kent <raven@themaw.net>
Cc: autofs@linux.kernel.org
Subject: Re: autofs4 past 2.6.38: how to make it work?
Date: Wed, 17 Aug 2011 12:42:07 +0400 [thread overview]
Message-ID: <4E4B7EDF.5020205@msgid.tls.msk.ru> (raw)
In-Reply-To: <1313569707.4418.32.camel@perseus.themaw.net>
17.08.2011 12:28, Ian Kent пишет:
> On Wed, 2011-08-17 at 10:27 +0400, Michael Tokarev wrote:
>> In 3.0, only two relevant commits are missing as far
>> as I can see: this negative autofs dentries fix, and
>> LOOKUP_CONTINUE change. The rest - again, ifaics -
>> are merely cosmetics. I'm not sure about this
>> LOOKUP_CONTINUE change, how relevant it is, but
>> the two combined does not look bad for -stable.
>> I think... :)
>
> Not sure what the LOOKUP_CONTINUE change is, what does it look like or
> do you have a git commit number?
commit 49084c3bb2055c401f3493c13edae14d49128ca0
Author: Al Viro <viro@zeniv.linux.org.uk>
Date: Sat Jun 25 21:59:52 2011 -0400
Subject: kill LOOKUP_CONTINUE
> There is actually one more change that needs to go in, although you
> might not see the problem. It is a fix for a lockdep problem.
Ah yeah, I've seen it too but haven't looked closely -- lockdep
is some "side" feature, even if I have it enabled.
Thanks,
/mjt
_______________________________________________
autofs mailing list
autofs@linux.kernel.org
http://linux.kernel.org/mailman/listinfo/autofs
next prev parent reply other threads:[~2011-08-17 8:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-15 19:38 autofs4 past 2.6.37: how to make it work? Michael Tokarev
2011-08-15 20:02 ` autofs4 past 2.6.38: " Michael Tokarev
2011-08-17 3:07 ` Ian Kent
2011-08-17 6:27 ` Michael Tokarev
2011-08-17 8:28 ` Ian Kent
2011-08-17 8:42 ` Michael Tokarev [this message]
2011-08-17 12:18 ` 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=4E4B7EDF.5020205@msgid.tls.msk.ru \
--to=mjt@tls.msk.ru \
--cc=autofs@linux.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 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.