From: syzbot <syzbot+735c2553ea82b2b34e82@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?] WARNING in pwq_release_workfn
Date: Sat, 04 May 2024 04:14:26 -0700 [thread overview]
Message-ID: <000000000000774a9006179ef0a2@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: 496bc5861c73 selftests: netfilter: nft_concat_range.sh: re..
git tree: net-next
console output: https://syzkaller.appspot.com/x/log.txt?x=14aa8897180000
kernel config: https://syzkaller.appspot.com/x/.config?x=15dda165e1d20cf1
dashboard link: https://syzkaller.appspot.com/bug?extid=735c2553ea82b2b34e82
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/507454068ec8/disk-496bc586.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/083381b27086/vmlinux-496bc586.xz
kernel image: https://storage.googleapis.com/syzbot-assets/4a1aaddd6e1a/bzImage-496bc586.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+735c2553ea82b2b34e82@syzkaller.appspotmail.com
------------[ cut here ]------------
WARNING: CPU: 0 PID: 3 at kernel/locking/lockdep.c:6465 lockdep_unregister_key+0x4cd/0x540 kernel/locking/lockdep.c:6465
Modules linked in:
CPU: 0 PID: 3 Comm: pool_workqueue_ Not tainted 6.9.0-rc5-syzkaller-01461-g496bc5861c73 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/27/2024
RIP: 0010:lockdep_unregister_key+0x4cd/0x540 kernel/locking/lockdep.c:6465
Code: 24 41 02 75 14 41 f7 c6 00 02 00 00 74 01 fb e8 29 b4 09 00 e9 83 fc ff ff e8 6f 25 0f 0a 41 f7 c6 00 02 00 00 75 e7 eb e6 90 <0f> 0b 90 eb 85 48 c7 c1 c0 fd a8 8f 80 e1 07 80 c1 03 38 c1 0f 8c
RSP: 0018:ffffc90000087cc0 EFLAGS: 00010002
RAX: 0000000000000000 RBX: 0000000000000000 RCX: dffffc0000000000
RDX: 0000000000000001 RSI: 0000000000000004 RDI: ffffc90000087c20
RBP: ffffc90000087da0 R08: 0000000000000003 R09: fffff52000010f84
R10: dffffc0000000000 R11: fffff52000010f84 R12: 00000000000003ee
R13: 1ffff92000010f9c R14: 0000000000000207 R15: ffffc90000087d00
FS: 0000000000000000(0000) GS:ffff8880b9400000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000000000000 CR3: 000000006272c000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
wq_unregister_lockdep kernel/workqueue.c:4655 [inline]
pwq_release_workfn+0x6e0/0x840 kernel/workqueue.c:4958
kthread_worker_fn+0x500/0xaf0 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:244
</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-05-04 11:14 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=000000000000774a9006179ef0a2@google.com \
--to=syzbot+735c2553ea82b2b34e82@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 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.