From: Theodore Tso <tytso@mit.edu>
To: hlily <tech.discuss@gmail.com>
Cc: linux-fsdevel@vger.kernel.org
Subject: Re: Ext3 question: How to compose an inode given a list of data block numbers?
Date: Thu, 8 Feb 2007 21:13:38 -0500 [thread overview]
Message-ID: <20070209021338.GB13207@thunk.org> (raw)
In-Reply-To: <8875903.post@talk.nabble.com>
On Thu, Feb 08, 2007 at 02:46:19PM -0800, hlily wrote:
>
> Suppose I have a list of data blocks, does Ext3 provide some functions that
> can help me to build a block list into an inode?
>
> If no such functions, could someone direct me to the right place in Ext3
> code that add block numbers to an inode?
What are you trying to do? Are you trying to do this from a kernel
module, or from user space?
- Ted
next prev parent reply other threads:[~2007-02-09 2:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-08 22:46 Ext3 question: How to compose an inode given a list of data block numbers? hlily
2007-02-09 2:13 ` Theodore Tso [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-02-08 22:35 hlily
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=20070209021338.GB13207@thunk.org \
--to=tytso@mit.edu \
--cc=linux-fsdevel@vger.kernel.org \
--cc=tech.discuss@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;
as well as URLs for NNTP newsgroup(s).