From: Shirish Pargaonkar <shirishpargaonkar@gmail.com>
To: linux-fsdevel@vger.kernel.org
Subject: handling inodes in lookup
Date: Tue, 3 Feb 2009 20:32:33 -0600 [thread overview]
Message-ID: <4a4634330902031832m607de084hee353b6353dc95e@mail.gmail.com> (raw)
I was working on handling lookup intents in cifs code.
So when in cifs lookup, we do a open after figuring out that is what
the intent is,
I do not know how to handle the generated and filled inode with the
info from open.
I do not think I can assign it to dentry and instantiate as vfs will
return with
EEXIST. So I am not sure what to do with the inode.
Your help is appreciated. FYI, I do not subscribe to this mailing list.
Regards,
Shirish
reply other threads:[~2009-02-04 2:32 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4a4634330902031832m607de084hee353b6353dc95e@mail.gmail.com \
--to=shirishpargaonkar@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
/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).