On Wednesday October 11, [email protected] wrote:
> >
> > I say "normally" because if a loop were created in the array->member
> > hierarchy a deadlock could happen. However that causes bigger
> > problems than a deadlock and should be fixed independently.
>
> ok to me. Sidenote: shouldnt we algorithmically forbid that "loop"
> scenario from occuring, as that possibility is what causes lockdep to
> complain about the worst-case scenario?
Yes we should. Possibly we could use the linkage information set up
by bd_claim_by_kobject. However I'm afraid that the locking required
to check that linkage safely will look very dead-lock prone to
lockdep. I suspect that can be worked-around though.
NeilBrown
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
