From: syzbot <syzbot+60f75ab7624f6e44392b@syzkaller.appspotmail.com>
To: bp@alien8.de, dave.hansen@linux.intel.com, hpa@zytor.com,
linux-kernel@vger.kernel.org, mingo@redhat.com,
netdev@vger.kernel.org, syzkaller-bugs@googlegroups.com,
tglx@linutronix.de, x86@kernel.org
Subject: [syzbot] [kernel?] BUG: using smp_processor_id() in preemptible code in pwq_release_workfn
Date: Wed, 27 Mar 2024 18:37:17 -0700 [thread overview]
Message-ID: <0000000000003d360f0614ae902b@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: 61df575632d6 libbpf: Add new sec_def "sk_skb/verdict"
git tree: bpf-next
console output: https://syzkaller.appspot.com/x/log.txt?x=17683185180000
kernel config: https://syzkaller.appspot.com/x/.config?x=6fb1be60a193d440
dashboard link: https://syzkaller.appspot.com/bug?extid=60f75ab7624f6e44392b
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/0d2d0f91bfad/disk-61df5756.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/0b0f2fd80260/vmlinux-61df5756.xz
kernel image: https://storage.googleapis.com/syzbot-assets/0450c835a85f/bzImage-61df5756.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+60f75ab7624f6e44392b@syzkaller.appspotmail.com
BUG: using smp_processor_id() in preemptible [00000000] code: pool_workqueue_/3
caller is pv_init_node kernel/locking/qspinlock_paravirt.h:284 [inline]
caller is __pv_queued_spin_lock_slowpath+0x192/0xc60 kernel/locking/qspinlock.c:439
CPU: 1 PID: 3 Comm: pool_workqueue_ Not tainted 6.8.0-syzkaller-05238-g61df575632d6 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/29/2024
Call Trace:
<TASK>
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0x1e7/0x2e0 lib/dump_stack.c:106
check_preemption_disabled+0x10e/0x120 lib/smp_processor_id.c:49
pv_init_node kernel/locking/qspinlock_paravirt.h:284 [inline]
__pv_queued_spin_lock_slowpath+0x192/0xc60 kernel/locking/qspinlock.c:439
pv_queued_spin_lock_slowpath arch/x86/include/asm/paravirt.h:584 [inline]
queued_spin_lock_slowpath+0x42/0x50 arch/x86/include/asm/qspinlock.h:51
queued_spin_lock include/asm-generic/qspinlock.h:114 [inline]
lockdep_lock+0x1b0/0x2b0 kernel/locking/lockdep.c:144
lockdep_unregister_key+0x20d/0x540 kernel/locking/lockdep.c:6456
wq_unregister_lockdep kernel/workqueue.c:4655 [inline]
pwq_release_workfn+0x6e0/0x840 kernel/workqueue.c:4958
kthread_worker_fn+0x4bf/0xab0 kernel/kthread.c:841
kthread+0x2f0/0x390 kernel/kthread.c:388
ret_from_fork+0x4b/0x80 arch/x86/kernel/process.c:147
ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:243
</TASK>
BUG: using __this_cpu_add() in preemptible [00000000] code: pool_workqueue_/3
caller is __pv_queued_spin_lock_slowpath+0x945/0xc60 kernel/locking/qspinlock.c:565
CPU: 1 PID: 3 Comm: pool_workqueue_ Not tainted 6.8.0-syzkaller-05238-g61df575632d6 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/29/2024
Call Trace:
<TASK>
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0x1e7/0x2e0 lib/dump_stack.c:106
check_preemption_disabled+0x10e/0x120 lib/smp_processor_id.c:49
__pv_queued_spin_lock_slowpath+0x945/0xc60 kernel/locking/qspinlock.c:565
pv_queued_spin_lock_slowpath arch/x86/include/asm/paravirt.h:584 [inline]
queued_spin_lock_slowpath+0x42/0x50 arch/x86/include/asm/qspinlock.h:51
queued_spin_lock include/asm-generic/qspinlock.h:114 [inline]
lockdep_lock+0x1b0/0x2b0 kernel/locking/lockdep.c:144
lockdep_unregister_key+0x20d/0x540 kernel/locking/lockdep.c:6456
wq_unregister_lockdep kernel/workqueue.c:4655 [inline]
pwq_release_workfn+0x6e0/0x840 kernel/workqueue.c:4958
kthread_worker_fn+0x4bf/0xab0 kernel/kthread.c:841
kthread+0x2f0/0x390 kernel/kthread.c:388
ret_from_fork+0x4b/0x80 arch/x86/kernel/process.c:147
ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:243
</TASK>
BUG: using __this_cpu_add() in preemptible [00000000] code: pool_workqueue_/3
caller is lockdep_unlock+0x16a/0x300 kernel/locking/lockdep.c:157
CPU: 1 PID: 3 Comm: pool_workqueue_ Not tainted 6.8.0-syzkaller-05238-g61df575632d6 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/29/2024
Call Trace:
<TASK>
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0x1e7/0x2e0 lib/dump_stack.c:106
check_preemption_disabled+0x10e/0x120 lib/smp_processor_id.c:49
lockdep_unlock+0x16a/0x300 kernel/locking/lockdep.c:157
lockdep_unregister_key+0x45c/0x540 kernel/locking/lockdep.c:6471
wq_unregister_lockdep kernel/workqueue.c:4655 [inline]
pwq_release_workfn+0x6e0/0x840 kernel/workqueue.c:4958
kthread_worker_fn+0x4bf/0xab0 kernel/kthread.c:841
kthread+0x2f0/0x390 kernel/kthread.c:388
ret_from_fork+0x4b/0x80 arch/x86/kernel/process.c:147
ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:243
</TASK>
---
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.
If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title
If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)
If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report
If you want to undo deduplication, reply with:
#syz undup
reply other threads:[~2024-03-28 1:37 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=0000000000003d360f0614ae902b@google.com \
--to=syzbot+60f75ab7624f6e44392b@syzkaller.appspotmail.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
--cc=x86@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).