On Tue, May 22, 2012 at 7:49 PM, Ian Kent <ikent@xxxxxxxxxx> wrote:
>
> The locking for the list traversal in get_next_positive_subdir() is
> wrong, so fix it.
As an explanation, this kind of thing is totally useless. It doesn't
actually give any information at all. It's like saying "change
locking"
What happened, and why? Why is the new nested spinlock ok and won't
deadlock against other nested users? Wazzup?
Linus
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
