From: "Arend van Spriel" <arend@broadcom.com>
To: "Peter Zijlstra" <peterz@infradead.org>,
"Ingo Molnar" <mingo@redhat.com>
Cc: "Tejun Heo" <tj@kernel.org>, LKML <linux-kernel@vger.kernel.org>
Subject: lockdep info message
Date: Fri, 26 Oct 2012 12:15:56 +0200 [thread overview]
Message-ID: <508A62DC.50805@broadcom.com> (raw)
Hi Peter and/or Ingo,
I am working on a driver (brcmfmac) and when unloading it or unplugging
the device I get this info message (see below) upon calling
cancel_work_sync(). Just wondering if there is something I need to do in
the driver or should it be done in workqueue code.
Regards,
Arend
[ 268.167897] INFO: trying to register non-static key.
[ 268.173279] the code is fine but needs lockdep annotation.
[ 268.179188] turning off the locking correctness validator.
[ 268.185093] Pid: 31, comm: khubd Tainted: G O
3.7.0-rc2-testing-lockdep #1
[ 268.193254] Call Trace:
[ 268.196150] [<c10929c6>] __lock_acquire+0xb36/0x1780
[ 268.201641] [<c10229fb>] ? lapic_next_event+0x1b/0x20
[ 268.207216] [<c108c0e2>] ? clockevents_program_event+0xb2/0x170
[ 268.213654] [<c108d4e9>] ? tick_program_event+0x29/0x30
[ 268.219404] [<c105f17d>] ? hrtimer_interrupt+0x17d/0x2b0
[ 268.225239] [<c133b170>] ? vt_console_print+0x280/0x350
[ 268.231000] [<c1093b14>] lock_acquire+0x84/0x120
[ 268.236152] [<c1053200>] ? delayed_work_timer_fn+0x30/0x30
[ 268.242172] [<c10943b4>] ? trace_hardirqs_on_caller+0xf4/0x180
[ 268.248541] [<c1053248>] flush_work+0x48/0x250
[ 268.253532] [<c1053200>] ? delayed_work_timer_fn+0x30/0x30
[ 268.259562] [<c109007b>] ? perf_trace_lock+0xb/0x120
[ 268.265075] [<c103af9a>] ? vprintk_emit+0x19a/0x500
[ 268.270503] [<c1054eea>] ? __cancel_work_timer+0x5a/0xb0
[ 268.276365] [<c10943b4>] ? trace_hardirqs_on_caller+0xf4/0x180
[ 268.282751] [<c1054efa>] __cancel_work_timer+0x6a/0xb0
[ 268.288426] [<c1054f6f>] cancel_work_sync+0xf/0x20
[ 268.293743] [<f843d71b>] brcmf_detach+0x7b/0xe0 [brcmfmac]
next reply other threads:[~2012-10-26 10:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-26 10:15 Arend van Spriel [this message]
2012-10-26 11:25 ` lockdep info message Peter Zijlstra
2012-10-26 13:19 ` Arend van Spriel
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=508A62DC.50805@broadcom.com \
--to=arend@broadcom.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=tj@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).