mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Bob Copeland <email@bobcopeland.com>
To: "pablo.ferlop@gmail.com" <pablo.ferlop@gmail.com>
Cc: Arjan van de Ven <arjan@infradead.org>, linux-kernel@vger.kernel.org
Subject: Re: string to inode conversion
Date: Sun, 15 Jan 2006 15:27:10 -0500	[thread overview]
Message-ID: <b6c5339f0601151227h33f511f2wbd581d02903c4145@mail.gmail.com> (raw)
In-Reply-To: <1137354577.11981.4.camel@localhost.localdomain>

On 1/15/06, pablo.ferlop@gmail.com <pablo.ferlop@gmail.com> wrote:
> Basically I'm trying to learn how sys_open() goes from char *filename to
> a struct inode. I know (or think) that sys_open() doesn't actually use a
> struct inode, but I wonder how that would go.

Look at ext2_lookup in fs/ext2/namei.c for example.  It depends on the
filesystem.

-Bob

      reply	other threads:[~2006-01-15 20:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-15 18:57 pablo.ferlop
2006-01-15 19:24 ` Arjan van de Ven
2006-01-15 19:49   ` pablo.ferlop
2006-01-15 20:27     ` Bob Copeland [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=b6c5339f0601151227h33f511f2wbd581d02903c4145@mail.gmail.com \
    --to=email@bobcopeland.com \
    --cc=arjan@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pablo.ferlop@gmail.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®