From: "pablo.ferlop@gmail.com" <pablo.ferlop@gmail.com>
To: Arjan van de Ven <arjan@infradead.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: string to inode conversion
Date: Sun, 15 Jan 2006 20:49:36 +0100 [thread overview]
Message-ID: <1137354577.11981.4.camel@localhost.localdomain> (raw)
In-Reply-To: <1137353054.3230.8.camel@laptopd505.fenrus.org>
Hi
This should be in kernel space, in the context of system calls.
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.
Thanks
El dom, 15-01-2006 a las 20:24 +0100, Arjan van de Ven escribió:
> On Sun, 2006-01-15 at 19:57 +0100, pablo.ferlop@gmail.com wrote:
> > Hi
> >
> > I was wondering how I can get from a string with a path like "/home" or
> > "/lib/libc-2.3.5.so" a struct inode.
>
> which namespace do you want this in? The init one? or the one from the
> user? (most traditional linux distributions only have one namespace, but
> now that COW namespaces are merged I expect distros to start
> experimenting with per user /tmp, or per-daemon data etc etc)
>
> This is not a trivial thing... you need a "context" into which you can
> ask that question (basically a process)
>
next prev parent reply other threads:[~2006-01-15 19:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-15 18:57 string to inode conversion pablo.ferlop
2006-01-15 19:24 ` Arjan van de Ven
2006-01-15 19:49 ` pablo.ferlop [this message]
2006-01-15 20:27 ` Bob Copeland
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=1137354577.11981.4.camel@localhost.localdomain \
--to=pablo.ferlop@gmail.com \
--cc=arjan@infradead.org \
--cc=linux-kernel@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