From: syzbot <syzbot+34813cbce633c9091556@syzkaller.appspotmail.com>
To: dhowells@redhat.com, linux-afs@lists.infradead.org,
linux-kernel@vger.kernel.org, marc.dionne@auristor.com,
syzkaller-bugs@googlegroups.com
Subject: [syzbot] [afs?] WARNING in delete_node (4)
Date: Mon, 06 Oct 2025 07:10:31 -0700 [thread overview]
Message-ID: <68e3cdd7.a00a0220.2a5ca.000b.GAE@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: 7f7072574127 Merge tag 'kbuild-6.18-1' of git://git.kernel..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=12c55942580000
kernel config: https://syzkaller.appspot.com/x/.config?x=8582d1234819ed79
dashboard link: https://syzkaller.appspot.com/bug?extid=34813cbce633c9091556
compiler: gcc (Debian 12.2.0-14+deb12u1) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: i386
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image (non-bootable): https://storage.googleapis.com/syzbot-assets/d900f083ada3/non_bootable_disk-7f707257.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/0e0a26398b43/vmlinux-7f707257.xz
kernel image: https://storage.googleapis.com/syzbot-assets/44d1286a1f5d/bzImage-7f707257.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+34813cbce633c9091556@syzkaller.appspotmail.com
------------[ cut here ]------------
WARNING: CPU: 3 PID: 33 at lib/radix-tree.c:572 delete_node+0x223/0x8d0 lib/radix-tree.c:572
Modules linked in:
CPU: 3 UID: 0 PID: 33 Comm: ksoftirqd/3 Not tainted syzkaller #0 PREEMPT(full)
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2~bpo12+1 04/01/2014
RIP: 0010:delete_node+0x223/0x8d0 lib/radix-tree.c:572
Code: 66 58 f6 41 bc 01 00 00 00 e8 49 ea 71 f6 44 89 e0 48 83 c4 28 5b 5d 41 5c 41 5d 41 5e 41 5f c3 cc cc cc cc e8 2e ea 71 f6 90 <0f> 0b 90 e8 25 ea 71 f6 48 c7 c6 90 88 48 8b 4c 89 e7 e8 a6 66 58
RSP: 0018:ffffc900005bfac0 EFLAGS: 00010246
RAX: 0000000000000000 RBX: ffff88802aec6160 RCX: ffffffff8b489df3
RDX: ffff88801bbea480 RSI: ffffffff8b489e82 RDI: ffff88802aec61a8
RBP: ffff888025afc000 R08: 0000000000000005 R09: 0000000000000000
R10: 0000000000000004 R11: 0000000000002b71 R12: ffff888025afc018
R13: dffffc0000000000 R14: 0000000000000000 R15: 0000000004000004
FS: 0000000000000000(0000) GS:ffff888097f66000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000000008001b000 CR3: 000000005e8cd000 CR4: 0000000000352ef0
Call Trace:
<TASK>
__radix_tree_delete+0x193/0x3d0 lib/radix-tree.c:1379
radix_tree_delete_item+0xea/0x230 lib/radix-tree.c:1430
afs_cell_destroy+0x1db/0x310 fs/afs/cell.c:523
rcu_do_batch kernel/rcu/tree.c:2605 [inline]
rcu_core+0x799/0x1530 kernel/rcu/tree.c:2861
handle_softirqs+0x219/0x8e0 kernel/softirq.c:622
run_ksoftirqd kernel/softirq.c:1063 [inline]
run_ksoftirqd+0x3a/0x60 kernel/softirq.c:1055
smpboot_thread_fn+0x3f4/0xae0 kernel/smpboot.c:160
kthread+0x3c2/0x780 kernel/kthread.c:463
ret_from_fork+0x56d/0x730 arch/x86/kernel/process.c:148
ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245
</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:[~2025-10-06 14:10 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=68e3cdd7.a00a0220.2a5ca.000b.GAE@google.com \
--to=syzbot+34813cbce633c9091556@syzkaller.appspotmail.com \
--cc=dhowells@redhat.com \
--cc=linux-afs@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.dionne@auristor.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 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.