It appears that bforget will lose the contents of a buffer
even if the buffer's contents are protected with the BH_Protected
flag. I am trying to understand if that is a bug in bforget, or
if it is a bug in cramfs that it calls bforget, causing destruction
of data when run on a ramdisk. Fixing either behavior is a small
patch. I would appreciate some advice on which component is at fault,
and I will be happy to generate the appropriate patch.
By the way, since the initial ramdisk's block size is 1024
and cramfs uses a block size of 4096, and set_blocksize destroys the
entire contents of the ramdisk if you change its block size, I have
also written a patch to fix this, which I will post with the cramfs/bforget
fix.
Adam J. Richter __ ______________ 4880 Stevens Creek Blvd, Suite 104
adam@yggdrasil.com \ / San Jose, California 95129-1034
+1 408 261-6630 | g g d r a s i l United States of America
fax +1 408 261-6631 "Free Software For The Rest Of Us."
-
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 : Wed May 31 2000 - 21:00:19 EST