No, it doesn't fix all the problems of ext2. It fixes only this one issue.
> b) doesn't fix anything that could be triggered - ext2_delete_entry()
> can happen only if you've already done lookup. I.e. no problems had been
> found in that block back when we were finding the entry.
That means there is no need to check dir in ext2_check_dir_entry(),
is there? If all callers to ext2_delete_entry() already verify the
buffer in ext2_find_entry() (which they appear to do), then there is
no point in calling ext2_check_dir_entry() at all.
> c) makes ugly code uglier.
Did you even look at the patch? I didn't ADD extra checks, I REMOVED the
(useless) checking for dir == NULL in ext2_check_dir_entry(). How can
that be "uglier"?
> d) real fix exists and got a lot of testing over that last 5 months.
Yes, I know all about it, I need it as part of the ext2 indexed directory
code. That doesn't mean your directory-in-pagecache will make it in to
2.4, so may as well fix the minor "problem" that exists now (it is not a
BUG, but a waste of a few cycles in a function that is called a LOT).
If your patch makes it into 2.4 then even better. If not, then my fix is
still better than leaving it as is, and it is "obviously correct" while
your patch changes a LOT of code.
Cheers, Andreas
-- Andreas Dilger \ "If a man ate a pound of pasta and a pound of antipasto, \ would they cancel out, leaving him still hungry?" http://www-mddsp.enel.ucalgary.ca/People/adilger/ -- Dogbert - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/