> 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
- how to write get_block? Mikulas Patocka
- Re: how to write get_block? Jan Kara
- Re: how to write get_block? Mikulas Patocka
- Re: how to write get_block? Alexander Viro
- Re: how to write get_block? Mikulas Patocka
- [possible race in ext2] Re: how to wri... Alexander Viro
- Re: [possible race in ext2] Re: h... Mikulas Patocka
- Re: [possible race in ext2] Re: h... Ingo Molnar
- Re: [possible race in ext2] R... Mikulas Patocka
- Re: [possible race in ext2] R... Alexander Viro
- Re: [possible race in ext... Matti Aarnio
- Re: [possible race in ext... Ingo Molnar
- [patch] [possible race in ext2] R... Mikulas Patocka
- Re: [patch] [possible race in... Andrea Arcangeli
- Re: [patch] [possible rac... Ingo Molnar
- Re: [patch] [possible rac... Andrea Arcangeli
- [patch] 2.3.20 simple fs-... Andrea Arcangeli
- Re: [patch] [possible rac... Stephen C. Tweedie
- Re: [patch] [possible rac... Alexander Viro