From: Oleg Drokin <green@clusterfs.com>
To: Ian Kent <raven@themaw.net>
Cc: Kernel Mailing List <linux-kernel@vger.kernel.org>, braam@clusterfs.com
Subject: Re: [3/9] Lustre VFS patches for 2.6
Date: Thu, 8 Jul 2004 09:57:57 +0300 [thread overview]
Message-ID: <20040708065757.GQ5619@linuxhacker.ru> (raw)
In-Reply-To: <Pine.LNX.4.58.0407080821140.30806@wombat.indigo.net.au>
Hello!
On Thu, Jul 08, 2004 at 08:27:26AM +0800, Ian Kent wrote:
> > + intent_init(&nd.intent.open, IT_OPEN);
> > nd.intent.open.flags = FMODE_READ;
> > - error = __user_walk(library, LOOKUP_FOLLOW|LOOKUP_OPEN, &nd);
> > + error = user_path_walk_it(library, &nd);
> I don't have source available right now (I'll check later) but droping
> LOOKUP_FOLLOW might break autofs4.
It is not dropped,
user_path_walk_it is defined like this:
#define user_path_walk_it(name,nd) \
__user_walk_it(name, LOOKUP_FOLLOW, nd)
Bye,
Oleg
prev parent reply other threads:[~2004-07-08 6:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-07 12:47 [3/9] Lustre VFS patches for 2.6 Oleg Drokin
2004-07-08 0:27 ` Ian Kent
2004-07-08 6:57 ` Oleg Drokin [this message]
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=20040708065757.GQ5619@linuxhacker.ru \
--to=green@clusterfs.com \
--cc=braam@clusterfs.com \
--cc=linux-kernel@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox