From: David Chow <davidchow@shaolinmicro.com>
To: Bryan Henderson <hbryan@us.ibm.com>
Cc: anil vijarnia <linux_fs@rediffmail.com>, linux-fsdevel@vger.kernel.org
Subject: Re: getting buffer of inode
Date: Sun, 23 Feb 2003 02:49:11 +0800 [thread overview]
Message-ID: <3E57C627.4070506@shaolinmicro.com> (raw)
In-Reply-To: OF65E68009.033BB829-ON87256CD4.0069E307-88256CD4.006A8EB9@us.ibm.com
Bryan Henderson wrote:
>
>
>
>
>>i'm trying to implement journaling in vfat (like in ext3).if i
>>have an inode structure how can i get the struct buffer_head
>>containing this inode structure.in ext2 the union in inode
>>structure conatins pointer to buffer,but there's no such pointer
>>in fat superblock.
>>can anyone please tell how to get buffer of this inode
>>structure.
>>
>>
>
>Since it's been a day and no one has responded, let me try to respond by
>saying I can't figure out what you're asking.
>
>Inodes don't have buffers that I know of. I don't find any union in the
>ext2 inode structure that contains a pointer to something I would call a
>buffer. I assume a buffer_head is a buffer head (struct buf), but I've
>never heard of a buffer head containing an inode structure.
>
No, I know what this man is asking. He probably new to buffer_head
operations and looked into the ext2 code. The union he refers to the
fs.h struct inode unions of all the fses. Of course, eventually
everything that read/write to block devices via buffer cache gets into
the buffer_heads. This is rather fs specific questions, many be some
hints on fs specific data (the union stuff in struct inode in fs.h). I
think this question really need to be answered by some vfat gurus as
they know about the on disk structure of the file system such that this
man can read that buffer properly from buffer cache.
One thing must be clear is that the struct inode in the dcache is
handled by VFS , although it is physically (on disk) describing some
inode structures. However, the struct inode is generated via the iget()
interface and fs specific driver fill in the blanks themselves. Hope
this give you some direction.
regards,
David Chow
prev parent reply other threads:[~2003-02-22 18:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-20 4:54 getting buffer of inode anil vijarnia
2003-02-21 19:25 ` Bryan Henderson
2003-02-22 18:49 ` David Chow [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=3E57C627.4070506@shaolinmicro.com \
--to=davidchow@shaolinmicro.com \
--cc=hbryan@us.ibm.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux_fs@rediffmail.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).