mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dave Kleikamp <shaggy@austin.ibm.com>
To: sankarshana rao <san_wipro@yahoo.com>
Cc: root@chaos.analogic.com, linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Inode question
Date: Thu, 22 Jul 2004 07:36:23 -0500	[thread overview]
Message-ID: <1090499783.17490.42.camel@shaggy.austin.ibm.com> (raw)
In-Reply-To: <20040721225752.90581.qmail@web50902.mail.yahoo.com>

On Wed, 2004-07-21 at 17:57, sankarshana rao wrote:
> Guys,
> Thx for the inputs...I got it with path_lookup....
> 
> Can I pass the inode pointer back to the user space???

You shouldn't do that.

> 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...

Couldn't the program chdir to the parent directory and create the
folders with a relative pathname?
-- 
David Kleikamp
IBM Linux Technology Center


  reply	other threads:[~2004-07-22 15:18 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
2004-07-22 12:36         ` Dave Kleikamp [this message]
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=1090499783.17490.42.camel@shaggy.austin.ibm.com \
    --to=shaggy@austin.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=root@chaos.analogic.com \
    --cc=san_wipro@yahoo.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®