From: Sasha Levin <sasha.levin@oracle.com>
To: Jan Kara <jack@suse.cz>, Tejun Heo <tj@kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: bdi: lockdep warning in bdi_queue_work
Date: Fri, 04 Apr 2014 18:06:37 -0400 [thread overview]
Message-ID: <533F2CED.3070006@oracle.com> (raw)
Hi all,
While fuzzing with trinity inside a KVM tools guest running the latest -next
kernel I've stumbled on the following:
[ 323.192041] INFO: trying to register non-static key.
[ 323.193083] the code is fine but needs lockdep annotation.
[ 323.193949] turning off the locking correctness validator.
[ 323.194687] CPU: 15 PID: 21793 Comm: trinity-c94 Not tainted 3.14.0-next-20140403-sasha-00019-g7474aa9-dirty #376
[ 323.196300] 0000000000000000 ffff8804d9067cf8 ffffffff954bfb2f 0000000000000000
[ 323.197522] ffffffff99378b10 ffff8804d9067df8 ffffffff921c3912 ffff88082bddaeb0
[ 323.198879] ffff880800000000 ffff880400000001 ffffffff00000000 ffff8804d9067d48
[ 323.200063] Call Trace:
[ 323.200487] dump_stack (lib/dump_stack.c:52)
[ 323.200581] __lock_acquire (kernel/locking/lockdep.c:743 kernel/locking/lockdep.c:3078)
[ 323.200581] ? __slab_alloc (mm/slub.c:2385 (discriminator 2))
[ 323.200581] ? __lock_acquire (kernel/locking/lockdep.c:3189)
[ 323.200581] ? kvm_clock_read (arch/x86/include/asm/preempt.h:90 arch/x86/kernel/kvmclock.c:86)
[ 323.200581] lock_acquire (arch/x86/include/asm/current.h:14 kernel/locking/lockdep.c:3602)
[ 323.200581] ? bdi_queue_work (arch/x86/include/asm/bitops.h:313 fs/fs-writeback.c:108)
[ 323.200581] _raw_spin_lock_bh (include/linux/spinlock_api_smp.h:136 kernel/locking/spinlock.c:175)
[ 323.200581] ? bdi_queue_work (arch/x86/include/asm/bitops.h:313 fs/fs-writeback.c:108)
[ 323.200581] bdi_queue_work (arch/x86/include/asm/bitops.h:313 fs/fs-writeback.c:108)
[ 323.200581] __bdi_start_writeback (fs/fs-writeback.c:141)
[ 323.200581] wakeup_flusher_threads (fs/fs-writeback.c:1077)
[ 323.200581] ? wakeup_flusher_threads (include/linux/rcupdate.h:800 fs/fs-writeback.c:1076)
[ 323.200581] ? syscall_trace_enter (include/linux/context_tracking.h:27 arch/x86/kernel/ptrace.c:1461)
[ 323.200581] sys_sync (fs/sync.c:107)
[ 323.200581] tracesys (arch/x86/kernel/entry_64.S:749)
Thanks,
Sasha
next reply other threads:[~2014-04-04 22:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-04 22:06 Sasha Levin [this message]
2014-04-07 10:21 ` bdi: lockdep warning in bdi_queue_work Jan Kara
2014-04-07 13:38 ` Sasha Levin
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=533F2CED.3070006@oracle.com \
--to=sasha.levin@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=jack@suse.cz \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.