From: Peter Zijlstra <peterz@infradead.org>
To: Dave Jones <davej@redhat.com>
Cc: netdev@vger.kernel.org
Subject: Re: irda: BUG: looking up invalid subclass: 4294967295
Date: Mon, 10 Feb 2014 22:39:59 +0100 [thread overview]
Message-ID: <20140210213959.GY2936@laptop.programming.kicks-ass.net> (raw)
In-Reply-To: <20140210213126.GA26078@redhat.com>
On Mon, Feb 10, 2014 at 04:31:26PM -0500, Dave Jones wrote:
> Is this irda being crap, or some weird lockdep corner case ?
>
> (no idea what the W taint was, some unrelated spew pushed it out
> of the dmesg buffer before it got chance to hit the log)
>
> Dave
>
> BUG: looking up invalid subclass: 4294967295
That's -1 if I'm not mistaken, that's indeed an invalid subclass.
> turning off the locking correctness validator.
> CPU: 0 PID: 1965 Comm: trinity-main Tainted: G W 3.14.0-rc1+ #108
> 00000000ffffffff 00000000a8765326 ffff880205ee7c40 ffffffff9872ae0a
> 00000000ffffffff ffff880205ee7c58 ffffffff9872732c ffff880084069730
> ffff880205ee7cd0 ffffffff980c10e2 000000010016000f 00000000ffffffff
> Call Trace:
> [<ffffffff9872ae0a>] dump_stack+0x4e/0x7a
> [<ffffffff9872732c>] look_up_lock_class.part.18+0x2f/0x34
> [<ffffffff980c10e2>] __lock_acquire.isra.28+0x722/0xa50
> [<ffffffff9873a01b>] ? preempt_count_sub+0x6b/0xf0
> [<ffffffff980c1b6d>] lock_acquire+0x8d/0x120
> [<ffffffffc05438f2>] ? hashbin_delete+0xf2/0x100 [irda]
> [<ffffffffc0545e30>] ? irias_delete_value+0x30/0x30 [irda]
> [<ffffffff987357fc>] _raw_spin_lock_irqsave_nested+0x4c/0x70
> [<ffffffffc05438f2>] ? hashbin_delete+0xf2/0x100 [irda]
> [<ffffffffc05438f2>] hashbin_delete+0xf2/0x100 [irda]
I tried looking at that code but gave up real quick.. That code is
'creative'.
prev parent reply other threads:[~2014-02-10 21:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-10 21:31 irda: BUG: looking up invalid subclass: 4294967295 Dave Jones
2014-02-10 21:39 ` Peter Zijlstra [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140210213959.GY2936@laptop.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=davej@redhat.com \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).