mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: syzbot <syzbot+89001660f14fb7684c83@syzkaller.appspotmail.com>
To: azpijr@gmail.com, davem@davemloft.net, dhowells@redhat.com,
	 edumazet@google.com, horms@kernel.org, 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: Re: [syzbot] [net?] [afs?] kernel BUG in rxrpc_destroy_all_connections (2)
Date: Sun, 27 Sep 2026 01:29:02 -0700	[thread overview]
Message-ID: <6ab8d3ce.dc2998a4.2261f5.0063.GAE@google.com> (raw)
In-Reply-To: <arjO9qbNdbvdi7ao@gmail.com>

Hello,

syzbot has tested the proposed patch but the reproducer is still triggering an issue:
kernel BUG in rxrpc_destroy_all_connections

bond0 (unregistering): (slave bond_slave_1): Releasing backup interface
bond0 (unregistering): Released all slaves
rxrpc: Assertion failed
------------[ cut here ]------------
kernel BUG at net/rxrpc/conn_object.c:488!
Oops: invalid opcode: 0000 [#1] SMP KASAN NOPTI
CPU: 2 UID: 0 PID: 13 Comm: kworker/u32:1 Not tainted syzkaller #0 PREEMPT(full) 
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2 04/01/2014
Workqueue: netns cleanup_net
RIP: 0010:rxrpc_destroy_all_connections.cold+0x12/0x14 net/rxrpc/conn_object.c:488
Code: ff 90 0f 0b e8 6e 97 99 00 48 c7 c7 20 73 5d 8d e8 72 be af ff 90 0f 0b e8 5a 97 99 00 48 c7 c7 20 73 5d 8d e8 5e be af ff 90 <0f> 0b e8 46 97 99 00 49 63 d6 48 83 ce ff 48 c7 c7 40 02 01 91 e8
RSP: 0018:ffffc90000107970 EFLAGS: 00010286
RAX: 0000000000000017 RBX: ffff888053d70000 RCX: 0000000000000000
RDX: 0000000000000017 RSI: ffffffff81ea1579 RDI: fffff52000020f1f
RBP: ffff888053d70064 R08: 0000000000000007 R09: 0000000000000000
R10: 8000000000000000 R11: 0000000000000001 R12: 1ffff92000020f30
R13: ffff888053d70078 R14: ffff888053d70088 R15: ffff888053d70088
FS:  0000000000000000(0000) GS:ffff8880d5d52000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00005562f0adc000 CR3: 000000002d8eb000 CR4: 0000000000352ef0
Call Trace:
 <TASK>
 rxrpc_exit_net+0x7b/0xc0 net/rxrpc/net_ns.c:113
 ops_exit_list net/core/net_namespace.c:200 [inline]
 ops_undo_list+0x2ee/0xab0 net/core/net_namespace.c:253
 cleanup_net+0x499/0x920 net/core/net_namespace.c:706
 process_one_work+0xac7/0x1b10 kernel/workqueue.c:3396
 process_scheduled_works kernel/workqueue.c:3479 [inline]
 worker_thread+0x5ef/0xe50 kernel/workqueue.c:3560
 kthread+0x373/0x450 kernel/kthread.c:436
 ret_from_fork+0x730/0xd60 arch/x86/kernel/process.c:158
 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245
 </TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:rxrpc_destroy_all_connections.cold+0x12/0x14 net/rxrpc/conn_object.c:488
Code: ff 90 0f 0b e8 6e 97 99 00 48 c7 c7 20 73 5d 8d e8 72 be af ff 90 0f 0b e8 5a 97 99 00 48 c7 c7 20 73 5d 8d e8 5e be af ff 90 <0f> 0b e8 46 97 99 00 49 63 d6 48 83 ce ff 48 c7 c7 40 02 01 91 e8
RSP: 0018:ffffc90000107970 EFLAGS: 00010286
RAX: 0000000000000017 RBX: ffff888053d70000 RCX: 0000000000000000
RDX: 0000000000000017 RSI: ffffffff81ea1579 RDI: fffff52000020f1f
RBP: ffff888053d70064 R08: 0000000000000007 R09: 0000000000000000
R10: 8000000000000000 R11: 0000000000000001 R12: 1ffff92000020f30
R13: ffff888053d70078 R14: ffff888053d70088 R15: ffff888053d70088
FS:  0000000000000000(0000) GS:ffff8880d5d52000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00005562f0adc000 CR3: 000000002d8eb000 CR4: 0000000000352ef0


Tested on:

commit:         a7bfaba4 ipv6: fix prefix route expiry in modify_prefi..
git tree:       https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git
console output: https://syzkaller.appspot.com/x/log.txt?x=16e8fd25580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=7d012d9c67977ee4
dashboard link: https://syzkaller.appspot.com/bug?extid=89001660f14fb7684c83
compiler:       gcc (Debian 14.2.0-19) 14.2.0, GNU ld (GNU Binutils for Debian) 2.44
patch:          https://syzkaller.appspot.com/x/patch.diff?x=159dda05580000


  reply	other threads:[~2026-09-27  8:29 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-06  0:12 [syzbot] [afs?] [net?] " syzbot
2026-09-22 14:57 ` [syzbot] [net?] [afs?] " syzbot
2026-09-27  7:40   ` Jose A. Perez de Azpillaga
2026-09-27  7:42     ` syzbot
2026-09-27  7:48       ` Jose A. Perez de Azpillaga
2026-09-27  7:50         ` syzbot
2026-09-27  8:14       ` Jose A. Perez de Azpillaga
2026-09-27  8:29         ` syzbot [this message]
2026-09-28 17:42         ` Pimyn Girgis
2026-09-27 11:08   ` Jose A. Perez de Azpillaga
2026-09-27 11:23     ` syzbot
2026-09-27 12:04   ` Jose A. Perez de Azpillaga
2026-09-27 12:19     ` syzbot

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=6ab8d3ce.dc2998a4.2261f5.0063.GAE@google.com \
    --to=syzbot+89001660f14fb7684c83@syzkaller.appspotmail.com \
    --cc=azpijr@gmail.com \
    --cc=davem@davemloft.net \
    --cc=dhowells@redhat.com \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --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

all inboxes | Powered by JetHome®