regarding file corruption bug in Linux kernel 2.6.19.x

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hello everyone...

I tried to read the explanation in LWN.net and kerneltrap.org but I can't still fully understand why file corruption bug happened. Here are my confusions

1. If a file backed page is made dirty, does this mean the buffer pages inside are automatically made dirty? Or is another function supposed to be called to mark these buffers (meaning the buffer head?) dirty?

2. When the filesystem layer decides to write back some blocks, is it done per page or per buffer? I got impression that it is done per buffer since buffer is the representation of disk block in memory, but please CMIIW

3. So, to mark that something must be sync-ed back to disk, is it enough to mark a page as dirty? Or do I also need to mark the buffer head as dirty (BH_dirty?) too? Are there any specific rules here?

4. It is mentioned that actually the problem arised since ext3 still effectively uses buffer head, while on the other hand Linus said buffer head should no longer be used as the indicator of dirtiness. Do I conclude correctly here?

Thank you in advance for your help.

regards,

Mulyadi


--
Kernelnewbies: Help each other learn about the Linux kernel.
Archive:       http://mail.nl.linux.org/kernelnewbies/
FAQ:           http://kernelnewbies.org/faq/


[Index of Archives]     [Newbies FAQ]     [Linux Kernel Mentors]     [Linux Kernel Development]     [IETF Annouce]     [Git]     [Networking]     [Security]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux SCSI]     [Linux ACPI]
  Powered by Linux