From: Greg KH <greg@kroah.com>
To: Artur Baruchi <mail.baruchi@gmail.com>
Cc: 7eggert@gmx.de, linux-kernel@vger.kernel.org
Subject: Re: Mapping Inode to File
Date: Fri, 22 Oct 2010 09:59:12 -0700 [thread overview]
Message-ID: <20101022165912.GA18639@kroah.com> (raw)
In-Reply-To: <AANLkTikebrSiW0unB8xy8UU1KNGaOZBu_HT=j9wQQeY5@mail.gmail.com>
A: No.
Q: Should I include quotations after my reply?
http://daringfireball.net/2007/07/on_top
On Fri, Oct 22, 2010 at 02:09:44PM -0200, Artur Baruchi wrote:
> Sorry, didnt understand your point.
>
> Could you please clarify?
The point is that, no, it's not simple to do this at all.
> Note that I need to retrieve the file name in Kernel Space, Im able to
> get the inode, but now I need to convert this inode to a name
> (something that I could use).
How about explaining why you need to get the file name from within the
kernel? Perhaps there's a better way to do what you are trying to
accomplish.
thanks,
greg k-h
next prev parent reply other threads:[~2010-10-22 17:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fGqN4-2Ns-3@gated-at.bofh.it>
2010-10-22 14:51 ` Mapping Inode to File Bodo Eggert
2010-10-22 16:09 ` Artur Baruchi
2010-10-22 16:59 ` Greg KH [this message]
2010-10-22 14:22 Artur Baruchi
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=20101022165912.GA18639@kroah.com \
--to=greg@kroah.com \
--cc=7eggert@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mail.baruchi@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