lkml.org 
[lkml]   [1999]   [Jan]   [28]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: RAMDISK Bug - 2.0.36 kernel (again)
Hi,

On Wed, 27 Jan 1999 17:19:16 +0000 (GMT), Bill Melotti
<billy@cognito.co.uk> said:
> Thanks for the reply. I thought the buffering was done at the block level
> and that the ramdisk code worked by basically setting the BH_Protected
> flag of the provided buffer on a write request (to prevent it ever get
> freed up) and if it should get a read request simply return zeroes,
> because there is no real block device to read. So even if files get
> deleted, that still involves writes to the block device and surely
> freeing the buffer might me you lose vital data from the filesystem
> structure.

Only the data blocks released will be freed in this way. All of the
inode tables and bitmap blocks which record the deletion of the data
still remain in the ramdisk.

--Stephen

-
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/

\
 
 \ /
  Last update: 2005-03-22 13:50    [from the cache]
©2003-2011 Jasper Spaans