Re: possible recursive locking detected: kseriod on 2.6.19-rc1-gb0eb0838

I don't know if this has been reported before, but here goes:

Thank you for the report. It is a false positive, we have a patch
to silence lockdep here.

Ahh, that explains it. I've looked at the code in question for half an hour and couldn't figure out what's wrong with the locking.

Cheers,
Roberto Nibali, ratz
--

echo '[q]sa[ln0=aln256%Pln256/snlbx]sb3135071790101768542287578439snlbxq' | dc

-
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/

---

• References:
  • possible recursive locking detected: kseriod on 2.6.19-rc1-gb0eb0838
    • From: Roberto Nibali <[email protected]>
  • Re: possible recursive locking detected: kseriod on 2.6.19-rc1-gb0eb0838
    • From: Dmitry Torokhov <[email protected]>

• Prev by Date: Re: [linux-usb-devel] error to be returned while suspended
• Next by Date: Re: [linux-usb-devel] error to be returned while suspended
• Previous by thread: Re: possible recursive locking detected: kseriod on 2.6.19-rc1-gb0eb0838
• Next by thread: [PATCH] md: use BUILD_BUG_ON
• Index(es):
  • Date
  • Thread

[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]