On Tue, Mar 22, 2011 at 11:39 AM, Al Viro <viro@xxxxxxxxxxxxxxxxxx> wrote:
>
> Locking analysis would be really nice; AFAICS, it violates locking order
> when called from e.g. ->setattr() and its protection against renames is
> nowhere near enough. I might be missing something subtle, but...
Miklos - have you tried using this with lockdep (together with the
same filesystems mounted natively too)? I'd expect that that should
show any bad lock usage..
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
