From: Harsha Srinath <harsha@usc.edu>
To: linux-fsdevel@vger.kernel.org
Subject: changes in fs.h and fsfilter.h
Date: Thu, 05 May 2005 17:53:59 -0700 [thread overview]
Message-ID: <427AC027.2070605@usc.edu> (raw)
I am trying to port a ext3 cow utility from 2.4 to 2.6. I have a
couple of questions that I figured is too ext3 specific for the
kernelnewbies list and am sincerely hoping I can find some help here.
1. In the the 2.4 ../include/linux/fs.h file, there is a union in the
VFS inode struct like :-
struct inode {
struct list_head i_hash;
struct list_head i_list;
struct list_head i_dentry;
........
union {
struct minix_inode_info minix_i;
struct ext2_inode_info ext2_i;
struct ext3_inode_info ext3_i;
.......
}u;
Can anyone tell me where this union info is present in 2.6.10 ? I
grep'ed in the ..../include/linux/ directory but could not find the
union in any VFS files. (I want the VFS to know my changed ext3 inode
info that I call "struct extcow3_inode_info extcow3_i".)
I guess the same answer would hold good for :-
struct super_block {
struct list_head s_list; /* Keep this first */
kdev_t s_dev;
unsigned long s_blocksize;
unsigned char s_blocksize_bits;
.........
union {
struct minix_sb_info minix_sb;
struct ext2_sb_info ext2_sb;
struct ext3_sb_info ext3_sb;
...............
}u;
2. I am unable to find the following #defines :-
#define FILTER_FS_TYPES 6
#define FILTER_FS_EXT2 0
#define FILTER_FS_EXT3 1
....................
that were earlier in ../include/linux/fsfilter.h in the 2.4 kernel.
Can anyone please tell me where this info is now? Again I tried
grep'ing into the files but could not find any file with that
information. I am a newbie and am not very sure what this info is too.
Can anyone shed some light please?
Thanks!
Harsha Srinath
next reply other threads:[~2005-05-06 0:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-06 0:53 Harsha Srinath [this message]
2005-05-06 17:54 ` changes in fs.h Bryan Henderson
2005-05-07 18:59 ` changes in fs.h and fsfilter.h Martin Jambor
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=427AC027.2070605@usc.edu \
--to=harsha@usc.edu \
--cc=linux-fsdevel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.