Re: ramdisk driver in 2.6.6 has a severe bug

[Andrew Morton]

viro@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx wrote:
>
> > Well in that case perhaps something else broke.  I've seen no such reports
>  > of recent regressions in the ramdisk driver.
>  > 
>  > The two problems of which I am aware are:
>  > 
>  > a) It loses its brains across umount.  Seems that it's very rare that
>  >    anyone actually cares about this, which is why it has not been fixed in
>  >    well over a year.
> 
>  Details, please.  The only case I'm aware of is when you have fs-set
>  block size different from the one we had before mount(2).  And in that
>  case it would lose its brains when the blocksize had been flipped in
>  the first place.  Which would tend to fail mount(2) anyway.

Oh, it's nothing to do with that.  Problem is that files backed by ramdisks
are marked "memory backed" so the writeback code doesn't write them to the
ramdisk inode.  So it's presently functioning as ramfs with ext2 metadata
in the blockdev inode.

I'll fix it up.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/