From: syzbot <syzbot+e1391a5bf3f779e31237@syzkaller.appspotmail.com>
To: davem@davemloft.net, dhowells@redhat.com, edumazet@google.com,
kuba@kernel.org, linux-afs@lists.infradead.org,
linux-kernel@vger.kernel.org, marc.dionne@auristor.com,
netdev@vger.kernel.org, pabeni@redhat.com,
syzkaller-bugs@googlegroups.com
Subject: [syzbot] kernel BUG in rxrpc_destroy_all_locals
Date: Tue, 06 Dec 2022 22:37:34 -0800 [thread overview]
Message-ID: <000000000000d878ce05ef372791@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: 15309fb26b87 net: sfp: clean up i2c-bus property parsing
git tree: net-next
console output: https://syzkaller.appspot.com/x/log.txt?x=15431383880000
kernel config: https://syzkaller.appspot.com/x/.config?x=c608c21151db14f2
dashboard link: https://syzkaller.appspot.com/bug?extid=e1391a5bf3f779e31237
compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/2919f1040d37/disk-15309fb2.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/2fb3e2516436/vmlinux-15309fb2.xz
kernel image: https://storage.googleapis.com/syzbot-assets/5638fcd36798/bzImage-15309fb2.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+e1391a5bf3f779e31237@syzkaller.appspotmail.com
------------[ cut here ]------------
kernel BUG at net/rxrpc/local_object.c:438!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
CPU: 1 PID: 4101 Comm: kworker/u4:7 Not tainted 6.1.0-rc7-syzkaller-01817-g15309fb26b87 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/26/2022
Workqueue: netns cleanup_net
RIP: 0010:rxrpc_destroy_all_locals+0xe8/0x180 net/rxrpc/local_object.c:438
Code: e8 dd bb 98 f8 48 83 eb 20 49 bd 00 00 00 00 00 fc ff df e8 ca bb 98 f8 48 85 db 75 19 e8 c0 bb 98 f8 4c 89 e7 e8 a8 79 0b 01 <0f> 0b 48 89 ef e8 8e 79 e6 f8 eb be e8 a7 bb 98 f8 48 8d 6b 14 be
RSP: 0018:ffffc9000d8a7be0 EFLAGS: 00010282
RAX: 0000000000000000 RBX: 0000000000000000 RCX: ffff8880295b3a80
RDX: 0000000000000000 RSI: 0000000000000008 RDI: ffffc9000d8a7b28
RBP: ffff8880494f3814 R08: 0000000000000001 R09: ffffc9000d8a7b2f
R10: fffff52001b14f65 R11: 0000000000000000 R12: ffff8880215f42e8
R13: dffffc0000000000 R14: dffffc0000000000 R15: fffffbfff1c2fe10
FS: 0000000000000000(0000) GS:ffff8880b9b00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fb41eed4620 CR3: 0000000027524000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
rxrpc_exit_net+0x174/0x300 net/rxrpc/net_ns.c:128
ops_exit_list+0xb0/0x170 net/core/net_namespace.c:169
cleanup_net+0x4ee/0xb10 net/core/net_namespace.c:606
process_one_work+0x9bf/0x1710 kernel/workqueue.c:2289
worker_thread+0x669/0x1090 kernel/workqueue.c:2436
kthread+0x2e8/0x3a0 kernel/kthread.c:376
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:306
</TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:rxrpc_destroy_all_locals+0xe8/0x180 net/rxrpc/local_object.c:438
Code: e8 dd bb 98 f8 48 83 eb 20 49 bd 00 00 00 00 00 fc ff df e8 ca bb 98 f8 48 85 db 75 19 e8 c0 bb 98 f8 4c 89 e7 e8 a8 79 0b 01 <0f> 0b 48 89 ef e8 8e 79 e6 f8 eb be e8 a7 bb 98 f8 48 8d 6b 14 be
RSP: 0018:ffffc9000d8a7be0 EFLAGS: 00010282
RAX: 0000000000000000 RBX: 0000000000000000 RCX: ffff8880295b3a80
RDX: 0000000000000000 RSI: 0000000000000008 RDI: ffffc9000d8a7b28
RBP: ffff8880494f3814 R08: 0000000000000001 R09: ffffc9000d8a7b2f
R10: fffff52001b14f65 R11: 0000000000000000 R12: ffff8880215f42e8
R13: dffffc0000000000 R14: dffffc0000000000 R15: fffffbfff1c2fe10
FS: 0000000000000000(0000) GS:ffff8880b9b00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fb41eed4620 CR3: 0000000026e44000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
---
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:[~2022-12-07 6: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=000000000000d878ce05ef372791@google.com \
--to=syzbot+e1391a5bf3f779e31237@syzkaller.appspotmail.com \
--cc=davem@davemloft.net \
--cc=dhowells@redhat.com \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-afs@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.dionne@auristor.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--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 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).