From: Sasha Levin <sasha.levin@oracle.com>
To: Greg KH <greg@kroah.com>, Tejun Heo <tj@kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: kernfs: trying to register non-static key in kernfs_iop_listxattr
Date: Tue, 01 Apr 2014 09:08:02 -0400 [thread overview]
Message-ID: <533ABA32.9080602@oracle.com> (raw)
Hi all,
While fuzzing with trinity inside a KVM tools guest running latest -next
kernel I've stumbled on the following:
[ 1316.776480] INFO: trying to register non-static key.
[ 1316.778981] the code is fine but needs lockdep annotation.
[ 1316.780364] turning off the locking correctness validator.
[ 1316.780364] CPU: 25 PID: 29352 Comm: trinity-c162 Not tainted 3.14.0-rc8-next-20140331-sasha-00013-g7a8780f #351
[ 1316.780364] 0000000000000000 ffff8805898cbc98 ffffffffbb4bc9a3 0000000000000000
[ 1316.780364] ffffffffbf375390 ffff8805898cbd98 ffffffffb81c3942 ffff8806ac800a70
[ 1316.780364] 0000000000000000 0000000100000001[child40:30166] Chose rand_syscalls. ffff880600000000 ffffffffb8330371
[ 1316.780364] Call Trace:
[ 1316.780364] dump_stack (lib/dump_stack.c:52)
[ 1316.780364] __lock_acquire (kernel/locking/lockdep.c:743 kernel/locking/lockdep.c:3078)
[ 1316.780364] ? listxattr (fs/xattr.c:550)
[ 1316.792691] ? listxattr (fs/xattr.c:550)
[ 1316.792691] ? debug_smp_processor_id (lib/smp_processor_id.c:57)
[ 1316.792691] ? __slab_alloc (mm/slub.c:2385 (discriminator 2))
[ 1316.792691] ? __this_cpu_preempt_check (lib/smp_processor_id.c:63)
[ 1316.792691] ? trace_hardirqs_on_caller (kernel/locking/lockdep.c:2557 kernel/locking/lockdep.c:2599)
[ 1316.792691] lock_acquire (arch/x86/include/asm/current.h:14 kernel/locking/lockdep.c:3602)
[ 1316.792691] ? simple_xattr_list (fs/xattr.c:982)
[ 1316.797929] ? sched_clock (arch/x86/include/asm/paravirt.h:192 arch/x86/kernel/tsc.c:305)
[ 1316.797929] _raw_spin_lock (include/linux/spinlock_api_smp.h:143 kernel/locking/spinlock.c:151)
[ 1316.797929] ? simple_xattr_list (fs/xattr.c:982)
[ 1316.797929] simple_xattr_list (fs/xattr.c:982)
[ 1316.797929] kernfs_iop_listxattr (fs/kernfs/inode.c:239)
[ 1316.797929] vfs_listxattr (fs/xattr.c:276)
[ 1316.797929] listxattr (fs/xattr.c:559)
[ 1316.797929] SyS_flistxattr (include/linux/file.h:38 fs/xattr.c:621 fs/xattr.c:612)
[ 1316.797929] ? tracesys (arch/x86/kernel/entry_64.S:738)
[ 1316.797929] tracesys (arch/x86/kernel/entry_64.S:749)
Thanks,
Sasha
reply other threads:[~2014-04-01 13:08 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=533ABA32.9080602@oracle.com \
--to=sasha.levin@oracle.com \
--cc=greg@kroah.com \
--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.