Re: [possible race in ext2] Re: how to write get_block?

Mikulas Patocka (mikulas@artax.karlin.mff.cuni.cz)
Fri, 8 Oct 1999 18:23:09 +0200 (CEST)

Messages sorted by: [ date ][ thread ][ subject ][ author ]
Next message: Sean Hunter: "Re: [linux-usb] Re: USB device allocation"
Previous message: Alexander Viro: "Re: how to write get_block?"

> yep we knew about this problem ... it's not quite an easy hack though.
> Putting the directory block cache (and symlink block cache) into the page
> cache would be the preferred method - this would also clean up the code
> alot i think.

If you knew about it, why didn't you fix it?? (or implement temporary
workaround: bforget(get_hash_table(...)) through all blocks if inode is
symlink or directory). It is serious! - it can cause data corruption. Such
bugs should be fixed immediatelly. Now, anybody using 2.3 has to worry
about his data. I'm switching back to good old 2.3.4.

Mikulas Patocka

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

Next message: Sean Hunter: "Re: [linux-usb] Re: USB device allocation"
Previous message: Alexander Viro: "Re: how to write get_block?"