"Ed Swierk":
> I get the same oops with this patch.
Thnak you for your testing.
> Can you shed any light on the debug message (in_atomic():1,
> irqs_disabled():0)? Is this situation due to a bug using spinlocks, or
> can there be another cause?
If you do spinlock, in_atomic() returns 1 but irq_disabled().
And I found unionfs_lookup_backend() in your stack trace, it reminds me
the spinlock in unionfs new_dentry_private_data(). But it seems to be
un-related.
You will be able to check by yourself, with inserting
printk("%d, %d\n", in_atomic(), irqs_disabled());
around spinlock in new_dentry_private_data().
Junjiro Okajima
_______________________________________________
unionfs mailing list
[email protected]
http://www.fsl.cs.sunysb.edu/mailman/listinfo/unionfs
