From: syzbot <syzbot+fa3ef895554bdbfd1183@syzkaller.appspotmail.com>
To: hdanton@sina.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [net?] WARNING in __unix_gc
Date: Fri, 02 Feb 2024 19:17:04 -0800 [thread overview]
Message-ID: <000000000000a8eeb4061071a9f6@google.com> (raw)
In-Reply-To: <20240203004122.1625-1-hdanton@sina.com>
Hello,
syzbot has tested the proposed patch but the reproducer is still triggering an issue:
WARNING in __unix_gc
------------[ cut here ]------------
WARNING: CPU: 1 PID: 11 at net/unix/garbage.c:350 __unix_gc+0xe90/0xec0 net/unix/garbage.c:350
Modules linked in:
CPU: 1 PID: 11 Comm: kworker/u4:0 Not tainted 6.8.0-rc2-syzkaller-g73c59d6fe109-dirty #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/25/2024
Workqueue: events_unbound __unix_gc
RIP: 0010:__unix_gc+0xe90/0xec0 net/unix/garbage.c:350
Code: 8b 04 25 28 00 00 00 48 3b 84 24 20 01 00 00 75 40 48 8d 65 d8 5b 41 5c 41 5d 41 5e 41 5f 5d c3 cc cc cc cc e8 31 9a 8b f7 90 <0f> 0b 90 eb 8e 48 8b 4c 24 08 80 e1 07 80 c1 03 38 c1 0f 8c e4 fb
RSP: 0018:ffffc90000107a80 EFLAGS: 00010293
RAX: ffffffff8a07bc2f RBX: 0000000000000000 RCX: ffff8880172ebb80
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: ffffc90000107bf0 R08: ffffffff8a07bbb3 R09: fffff52000020f40
R10: dffffc0000000000 R11: fffff52000020f40 R12: 1ffff92000020f5e
R13: ffffc90000107ae0 R14: ffffc90000107ae0 R15: dffffc0000000000
FS: 0000000000000000(0000) GS:ffff8880b9500000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f83579e65e8 CR3: 000000000df34000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
process_one_work kernel/workqueue.c:2633 [inline]
process_scheduled_works+0x973/0x14b0 kernel/workqueue.c:2706
worker_thread+0xa5f/0x1000 kernel/workqueue.c:2787
kthread+0x2ef/0x390 kernel/kthread.c:388
ret_from_fork+0x4b/0x80 arch/x86/kernel/process.c:147
ret_from_fork_asm+0x1b/0x30 arch/x86/entry/entry_64.S:242
</TASK>
Tested on:
commit: 73c59d6f Merge branch 'net-sched-load-modules-via-alias'
git tree: net-next
console output: https://syzkaller.appspot.com/x/log.txt?x=14fdf6ffe80000
kernel config: https://syzkaller.appspot.com/x/.config?x=a2ad00c8608f36a5
dashboard link: https://syzkaller.appspot.com/bug?extid=fa3ef895554bdbfd1183
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
patch: https://syzkaller.appspot.com/x/patch.diff?x=1384e09fe80000
next prev parent reply other threads:[~2024-02-03 3:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-02 13:26 [syzbot] [net?] WARNING in __unix_gc syzbot
2024-02-03 0:41 ` Hillf Danton
2024-02-03 3:17 ` syzbot [this message]
2024-02-03 4:00 ` Kuniyuki Iwashima
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=000000000000a8eeb4061071a9f6@google.com \
--to=syzbot+fa3ef895554bdbfd1183@syzkaller.appspotmail.com \
--cc=hdanton@sina.com \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
/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.