From: sankarshana rao <san_wipro@yahoo.com>
To: root@chaos.analogic.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: Inode question
Date: Wed, 21 Jul 2004 15:57:52 -0700 (PDT) [thread overview]
Message-ID: <20040721225752.90581.qmail@web50902.mail.yahoo.com> (raw)
In-Reply-To: <Pine.LNX.4.53.0407211708040.18371@chaos>
Guys,
Thx for the inputs...I got it with path_lookup....
Can I pass the inode pointer back to the user space???
I have a scenario in which I have to create multiple
folders on the harddisk. The number of folders can be
in hundreds. Instead of parsing the path name
everytime I need to create a folder (that's what
sys_mkdir does??? ), I was thinking if I have the
inode* of the parent folder, I can avoid this parsing
and directly create a subfolder under the parent
folder...
Pls advice if this approach makes sense or not and if
it is doable or not??
any input in this regard will be very helpful..
--- "Richard B. Johnson" <root@chaos.analogic.com>
wrote:
> On Wed, 21 Jul 2004, sankarshana rao wrote:
>
> > Thx for the reply...
> > When I try to call lookup() from my kernel module,
> it
> > gives undefined symbol error during INSMOD..
> > any clues???
> >
>
> It's probably not an exported symbol.
>
> Cheers,
> Dick Johnson
> Penguin : Linux version 2.4.26 on an i686 machine
> (5570.56 BogoMips).
> Note 96.31% of all statistics are
> fiction.
>
>
>
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
next prev parent reply other threads:[~2004-07-21 22:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-21 18:39 sankarshana rao
2004-07-21 20:25 ` Dave Kleikamp
2004-07-21 20:46 ` sankarshana rao
2004-07-21 20:56 ` Dave Kleikamp
2004-07-21 21:09 ` Richard B. Johnson
2004-07-21 22:57 ` sankarshana rao [this message]
2004-07-22 12:36 ` Dave Kleikamp
2004-07-22 14:23 ` Paulo Marques
2004-07-27 1:28 ` sankarshana rao
2004-07-27 11:18 ` Paulo Marques
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=20040721225752.90581.qmail@web50902.mail.yahoo.com \
--to=san_wipro@yahoo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=root@chaos.analogic.com \
/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
all inboxes | Powered by JetHome®