Hi,
On Mon, 10 Apr 2000 10:51:50 +0100, Stephen C. Tweedie wrote:
> There is nothing in Linux which enforces this. You do need to have
> a block device to identify a fs superblock, but there is no reason why
> the filesystem cannot access other block devices too. Ext3 will be
> using this to place the journal on a separate disk from the main
> filesystem, and we have had patches against ext2 in the past to allow
> the filesystem to span multiple block devices.
> As far as the block device layer is concerned, all you do is submit
> block IO requests to devices. It doesn't care which devices, and it
> doesn't care who is doing the IO.
I have been trying to figure this out. It looks like to get a reference
to the block device I should call bdget, usually followed by a
blkdev_get.
If I want to write a module, both symbols are kindly exported with an
EXPORT_SYMBOL in kernel/ksyms.c. However, to clean up on module exit,
only blkdev_put is exported, not bdput. Shouldn't bdput be exported as
well ?
Mark
--- v2.3.99-pre5/linux/kernel/ksyms.c Fri Apr 7 16:38:00 2000
+++ linux/kernel/ksyms.c Sat Apr 15 09:24:17 2000
@@ -179,6 +179,7 @@
EXPORT_SYMBOL(set_blocksize);
EXPORT_SYMBOL(getblk);
EXPORT_SYMBOL(bdget);
+EXPORT_SYMBOL(bdput);
EXPORT_SYMBOL(bread);
EXPORT_SYMBOL(breada);
EXPORT_SYMBOL(__brelse);
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sat Apr 15 2000 - 21:00:26 EST