From: syzbot <syzbot+1b5d053eb77554ea5d77@syzkaller.appspotmail.com>
To: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com, viro@zeniv.linux.org.uk
Subject: BUG: spinlock bad magic in try_to_wake_up
Date: Tue, 08 Sep 2020 00:32:22 -0700 [thread overview]
Message-ID: <000000000000f69d8405aec8552b@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: b765a32a Merge tag 'scsi-fixes' of git://git.kernel.org/pu..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=13188279900000
kernel config: https://syzkaller.appspot.com/x/.config?x=e1c560d0f4e121c9
dashboard link: https://syzkaller.appspot.com/bug?extid=1b5d053eb77554ea5d77
compiler: clang version 10.0.0 (https://github.com/llvm/llvm-project/ c2443155a0fb245c8f17f2c1c72b6ea391e86e81)
Unfortunately, I don't have any reproducer for this issue yet.
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+1b5d053eb77554ea5d77@syzkaller.appspotmail.com
BUG: spinlock bad magic on CPU#0, systemd-udevd/3905
lock: 0xffff888000146cc8, .magic: 000f0f00, .owner: <none>/-1, .owner_cpu: -1
CPU: 0 PID: 3905 Comm: systemd-udevd Not tainted 5.9.0-rc3-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Call Trace:
__dump_stack lib/dump_stack.c:77 [inline]
dump_stack+0x1d6/0x29e lib/dump_stack.c:118
spin_dump kernel/locking/spinlock_debug.c:67 [inline]
spin_bug kernel/locking/spinlock_debug.c:75 [inline]
debug_spin_lock_before kernel/locking/spinlock_debug.c:83 [inline]
do_raw_spin_lock+0x2cc/0x800 kernel/locking/spinlock_debug.c:112
__raw_spin_lock_irqsave include/linux/spinlock_api_smp.h:117 [inline]
_raw_spin_lock_irqsave+0xb6/0xd0 kernel/locking/spinlock.c:159
try_to_wake_up+0x5f/0xbb0 kernel/sched/core.c:2859
autoremove_wake_function+0x12/0x110 kernel/sched/wait.c:389
__wake_up_common+0x30a/0x4e0 kernel/sched/wait.c:93
__wake_up_common_lock kernel/sched/wait.c:123 [inline]
__wake_up+0xd4/0x150 kernel/sched/wait.c:142
ep_poll_callback+0x50e/0x910 fs/eventpoll.c:1273
__wake_up_common+0x30a/0x4e0 kernel/sched/wait.c:93
__wake_up_common_lock kernel/sched/wait.c:123 [inline]
__wake_up_sync_key+0xd3/0x150 kernel/sched/wait.c:190
sock_def_readable+0x10f/0x210 net/core/sock.c:2908
__netlink_sendskb net/netlink/af_netlink.c:1251 [inline]
netlink_sendskb+0x8d/0x130 net/netlink/af_netlink.c:1257
netlink_unicast+0x5b2/0x940 net/netlink/af_netlink.c:1345
netlink_sendmsg+0xa57/0xd70 net/netlink/af_netlink.c:1919
sock_sendmsg_nosec net/socket.c:651 [inline]
sock_sendmsg net/socket.c:671 [inline]
____sys_sendmsg+0x519/0x800 net/socket.c:2353
___sys_sendmsg net/socket.c:2407 [inline]
__sys_sendmsg+0x2b1/0x360 net/socket.c:2440
do_syscall_64+0x31/0x70 arch/x86/entry/common.c:46
entry_SYSCALL_64_after_hwframe+0x44/0xa9
RIP: 0033:0x7fb6a57a8e67
Code: 89 02 48 c7 c0 ff ff ff ff eb d0 0f 1f 84 00 00 00 00 00 8b 05 6a b5 20 00 85 c0 75 2e 48 63 ff 48 63 d2 b8 2e 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 01 c3 48 8b 15 11 71 20 00 f7 d8 64 89 02 48
RSP: 002b:00007ffcc6917278 EFLAGS: 00000246 ORIG_RAX: 000000000000002e
RAX: ffffffffffffffda RBX: 000056206161bcb0 RCX: 00007fb6a57a8e67
RDX: 0000000000000000 RSI: 00007ffcc6917290 RDI: 0000000000000004
RBP: 00007ffcc6917290 R08: 000056206161bdf4 R09: 0000000000000000
R10: 0000000000000018 R11: 0000000000000246 R12: 000056206162d8c0
R13: 000000000000009b R14: 0000562061620970 R15: 0000000000000000
---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzkaller@googlegroups.com.
syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
reply other threads:[~2020-09-08 7:32 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=000000000000f69d8405aec8552b@google.com \
--to=syzbot+1b5d053eb77554ea5d77@syzkaller.appspotmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=viro@zeniv.linux.org.uk \
/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.