INFO: trying to register non-static key in remove_wait_queue

20 views
Skip to first unread message

syzbot

unread,
Dec 23, 2017, 7:59:04 AM12/23/17
to linux-...@vger.kernel.org, mi...@redhat.com, pet...@infradead.org, syzkall...@googlegroups.com
Hello,

syzkaller hit the following crash on
6084b576dca2e898f5c101baef151f7bfdbb606d
git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/master
compiler: gcc (GCC) 7.1.1 20170620
.config is attached
Raw console output is attached.

Unfortunately, I don't have any reproducer for this bug yet.


binder: 16148:16168 ERROR: BC_REGISTER_LOOPER called without request
binder: 16148:16155 ioctl 40046207 0 returned -16
INFO: trying to register non-static key.
the code is fine but needs lockdep annotation.
turning off the locking correctness validator.
CPU: 1 PID: 16155 Comm: syz-executor7 Not tainted 4.15.0-rc3-next-20171214+
#67
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
Google 01/01/2011
Call Trace:
__dump_stack lib/dump_stack.c:17 [inline]
dump_stack+0xe9/0x14b lib/dump_stack.c:53
register_lock_class+0x164/0x5d0 kernel/locking/lockdep.c:752
__lock_acquire+0xb4/0x1430 kernel/locking/lockdep.c:3314
lock_acquire+0xbf/0x220 kernel/locking/lockdep.c:3914
__raw_spin_lock_irqsave include/linux/spinlock_api_smp.h:110 [inline]
_raw_spin_lock_irqsave+0x56/0x70 kernel/locking/spinlock.c:152
remove_wait_queue+0x14/0x60 kernel/sched/wait.c:50
ep_remove_wait_queue fs/eventpoll.c:595 [inline]
ep_unregister_pollwait.isra.7+0x79/0x1f0 fs/eventpoll.c:613
ep_free+0x71/0x140 fs/eventpoll.c:830
ep_eventpoll_release+0x26/0x30 fs/eventpoll.c:862
__fput+0x120/0x270 fs/file_table.c:209
____fput+0x15/0x20 fs/file_table.c:243
task_work_run+0xa3/0xe0 kernel/task_work.c:113
exit_task_work include/linux/task_work.h:22 [inline]
do_exit+0x3e6/0x1050 kernel/exit.c:869
do_group_exit+0x60/0x100 kernel/exit.c:972
get_signal+0x36c/0xad0 kernel/signal.c:2337
do_signal+0x23/0x670 arch/x86/kernel/signal.c:809
exit_to_usermode_loop+0x13c/0x160 arch/x86/entry/common.c:161
prepare_exit_to_usermode arch/x86/entry/common.c:195 [inline]
syscall_return_slowpath+0x1b4/0x1e0 arch/x86/entry/common.c:264
entry_SYSCALL_64_fastpath+0x94/0x96
RIP: 0033:0x452a09
RSP: 002b:00007fa6f41b8c58 EFLAGS: 00000212 ORIG_RAX: 0000000000000010
RAX: fffffffffffffff0 RBX: 000000000071bea0 RCX: 0000000000452a09
RDX: 0000000000000000 RSI: 0000000040046207 RDI: 0000000000000015
RBP: 0000000000000161 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000212 R12: 00000000006ef1b8
R13: 00000000ffffffff R14: 00007fa6f41b96d4 R15: 0000000000000000


---
This bug is generated by a dumb bot. It may contain errors.
See https://goo.gl/tpsmEJ for details.
Direct all questions to syzk...@googlegroups.com.
Please credit me with: Reported-by: syzbot <syzk...@googlegroups.com>

syzbot will keep track of this bug report.
Once a fix for this bug is merged into any tree, reply to this email with:
#syz fix: exact-commit-title
To mark this as a duplicate of another syzbot report, please reply with:
#syz dup: exact-subject-of-another-report
If it's a one-off invalid bug report, please reply with:
#syz invalid
Note: if the crash happens again, it will cause creation of a new bug
report.
Note: all commands must start from beginning of the line in the email body.
config.txt
raw.log

Dmitry Vyukov

unread,
Feb 13, 2018, 3:03:50 PM2/13/18
to syzbot, syzkall...@googlegroups.com
old bug bankruptcy

#syz invalid

On Sat, Dec 23, 2017 at 1:59 PM, syzbot
<bot+524a8fc8be5eada475...@syzkaller.appspotmail.com>
wrote:
> --
> You received this message because you are subscribed to the Google Groups
> "syzkaller-bugs" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to syzkaller-bug...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/syzkaller-bugs/001a1146f1143c8fab0561017f61%40google.com.
> For more options, visit https://groups.google.com/d/optout.
Reply all
Reply to author
Forward
0 new messages