INFO: trying to register non-static key in free_ipcs

8 views
Skip to first unread message

syzbot

unread,
Dec 19, 2017, 5:52:04 AM12/19/17
to ak...@linux-foundation.org, elena.r...@intel.com, gre...@linuxfoundation.org, gscr...@redhat.com, guillaum...@supersonicimagine.com, kees...@chromium.org, linux-...@vger.kernel.org, mi...@kernel.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.


9pnet_virtio: no channels available for device ./file0
Buffer I/O error on dev loop0, logical block 0, async page read
INFO: trying to register non-static key.
the code is fine but needs lockdep annotation.
turning off the locking correctness validator.
CPU: 1 PID: 21631 Comm: syz-executor2 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 include/linux/spinlock_api_smp.h:142 [inline]
_raw_spin_lock+0x2a/0x40 kernel/locking/spinlock.c:144
spin_lock include/linux/spinlock.h:310 [inline]
ipc_lock_object ipc/util.h:171 [inline]
free_ipcs+0xc5/0x140 ipc/namespace.c:123
sem_exit_ns+0x20/0x40 ipc/sem.c:200
free_ipc_ns ipc/namespace.c:132 [inline]
put_ipc_ns+0x55/0xd0 ipc/namespace.c:164
free_nsproxy+0x63/0x100 kernel/nsproxy.c:180
switch_task_namespaces+0x80/0x90 kernel/nsproxy.c:229
exit_task_namespaces+0x17/0x20 kernel/nsproxy.c:234
do_exit+0x3e1/0x1050 kernel/exit.c:868
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:0x452a39
RSP: 002b:00007f0c9c350c58 EFLAGS: 00000212 ORIG_RAX: 000000000000011d
RAX: fffffffffffffffb RBX: 00000000007580d8 RCX: 0000000000452a39
RDX: 0000000000000000 RSI: 0000000000000011 RDI: 000000000000001c
RBP: 000000000000006c R08: 0000000000000000 R09: 0000000000000000
R10: 0000000044400004 R11: 0000000000000212 R12: 00000000006eeac0
R13: 00000000ffffffff R14: 00007f0c9c3516d4 R15: 000000000000000c
audit: type=1400 audit(1513383346.376:11455): avc: denied { sys_ptrace }
for pid=21695 comm="ps" capability=19
scontext=system_u:system_r:kernel_t:s0
tcontext=system_u:system_r:kernel_t:s0 tclass=cap_userns permissive=1
QAT: Invalid ioctl
QAT: Invalid ioctl
QAT: Invalid ioctl
QAT: Invalid ioctl


---
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:00:24 PM2/13/18
to syzbot, syzkall...@googlegroups.com
old bug bankruptcy

#syz invalid

On Tue, Dec 19, 2017 at 11:52 AM, syzbot
<bot+020b386f35de269c77...@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/94eb2c05a522bc7e1f0560af4141%40google.com.
> For more options, visit https://groups.google.com/d/optout.
Reply all
Reply to author
Forward
0 new messages