Hugh Dickins wrote:
> It seems that __lookup() can easily return 0, even though there's
> more to find, if it starts partway into a RADIX_TREE_MAP_SIZE
> array, in which the only occupied slots are before it starts.
erk. That sounds right.
I don't think the max_index test matters much - if we ever
hit that index then something has gone horridly wrong, because
it's out-of-bounds for the tree height. But whatever.
> Patch below seems to fix it
But your patch only fixes the symptoms of the bug. You should
fix the real bug. But to do that you'd need to find me, so this
will have to do for now.
> but I bet you can improve upon it.
Well the colour scheme is a bit gaudy.
> Might this relate to Trond/Chuck's NFS invalidation woes?
Nope; this code is only in the mm crash-test-dummy tree at present.
And it's currently at the "wow, it worked first time" stage. I need
to get down and write some special test code for it, and to run
fsx-linux. Possibly fsx-linux has sufficient coverage.
> It's certainly the main contributor to my tmpfs problems.
Sorry about that.
> I look forward to your "erk" - or will you delight us with
> some other exclamation?!
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to firstname.lastname@example.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Mon Sep 23 2002 - 22:00:24 EST