lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [day] [month] [year] [list]
Message-ID: <CAL==pd23yRnG8B-5bhr2bChPBvPLsrmQ9EkjC8FfANYxttCdzw@mail.gmail.com>
Date:	Tue, 13 Sep 2011 20:26:13 -0400
From:	shweta saxena <shweta0232@...il.com>
To:	linux-ext4@...r.kernel.org
Subject: Storing inode block device information in struct sb_info

 I am trying to separate metadata from data and mount it seperately on
a block device.I have an idea abt how to separate it ,  a) Parsing a
new inode device mount point b) Storing inode block device information
in struct sb_info

I had some doubts and confusions related to storing the inode block
device information in struct ext4_sb_info.
I am not sure about how to go about doing it. I guess that it can be
done by mounting the block device in the VFS first and then storing it
in struct ext4_sb_info in ext4.h header file.

Any help would be really appreciated.
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ