[v5.15] INFO: rcu detected stall in ext4_ioctl

0 views
Skip to first unread message

syzbot

unread,
Sep 23, 2023, 1:20:12 PM9/23/23
to syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: b911329317b4 Linux 5.15.133
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1708480a680000
kernel config: https://syzkaller.appspot.com/x/.config?x=a9c9f0083f439f72
dashboard link: https://syzkaller.appspot.com/bug?extid=dbb4ae0e986657890b1c
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/46530025981a/disk-b9113293.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/d27830145a50/vmlinux-b9113293.xz
kernel image: https://storage.googleapis.com/syzbot-assets/ee1d0b88a1d9/bzImage-b9113293.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+dbb4ae...@syzkaller.appspotmail.com

ip6_tunnel: ip6tnl1 xmit: Local address not yet configured!
ip6_tunnel: ip6tnl1 xmit: Local address not yet configured!
ip6_tunnel: ip6tnl1 xmit: Local address not yet configured!
rcu: INFO: rcu_preempt detected stalls on CPUs/tasks:
rcu: 0-...0: (1 GPs behind) idle=15f/1/0x4000000000000000 softirq=25004/25005 fqs=2100
(detected by 1, t=10506 jiffies, g=34781, q=618)
Sending NMI from CPU 1 to CPUs 0:
NMI backtrace for cpu 0
CPU: 0 PID: 8464 Comm: syz-executor.1 Not tainted 5.15.133-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/04/2023
RIP: 0010:_raw_spin_lock_irqsave+0xa/0x120 kernel/locking/spinlock.c:161
Code: c9 ff 74 24 08 e8 46 f6 3c f7 48 83 c4 08 48 89 df 5b e9 59 6a 3e f7 66 0f 1f 84 00 00 00 00 00 55 48 89 e5 41 57 41 56 41 55 <41> 54 53 48 83 e4 e0 48 83 ec 60 49 89 fe 65 48 8b 04 25 28 00 00
RSP: 0018:ffffc90000007bd8 EFLAGS: 00000006
RAX: 000ffff8880743e3 RBX: 0000000000000000 RCX: 0000000000011288
RDX: 0000000000000010 RSI: 0000000000000000 RDI: ffffffff91616930
RBP: ffffc90000007bf0 R08: dffffc0000000000 R09: ffffc90000007c60
R10: 0000000000000000 R11: dffffc0000000001 R12: dffffc0000000000
R13: ffffffff91616928 R14: ffff8880743e3b40 R15: dffffc0000000000
FS: 00007fcefc6e06c0(0000) GS:ffff8880b9a00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000001b3062d000 CR3: 000000001d057000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<NMI>
</NMI>
<IRQ>
debug_object_activate+0x166/0x860 lib/debugobjects.c:693
debug_hrtimer_activate kernel/time/hrtimer.c:420 [inline]
debug_activate kernel/time/hrtimer.c:475 [inline]
enqueue_hrtimer+0x30/0x310 kernel/time/hrtimer.c:1084
__run_hrtimer kernel/time/hrtimer.c:1702 [inline]
__hrtimer_run_queues+0x6b6/0xcf0 kernel/time/hrtimer.c:1749
hrtimer_interrupt+0x392/0x980 kernel/time/hrtimer.c:1811
local_apic_timer_interrupt arch/x86/kernel/apic/apic.c:1085 [inline]
__sysvec_apic_timer_interrupt+0x139/0x470 arch/x86/kernel/apic/apic.c:1102
sysvec_apic_timer_interrupt+0x8c/0xb0 arch/x86/kernel/apic/apic.c:1096
</IRQ>
<TASK>
asm_sysvec_apic_timer_interrupt+0x16/0x20 arch/x86/include/asm/idtentry.h:638
RIP: 0010:get_stack_info+0xb8/0xf0 arch/x86/kernel/dumpstack_64.c:213
Code: 48 c7 c7 71 5c 13 8c e8 d0 e8 ed 08 eb cf be 01 00 00 00 48 c7 c7 c0 7f 75 8c 4c 89 e2 e8 e0 9c fb 02 4d 0f a3 e5 72 9f 8b 1b <48> 83 fb 40 73 0f b8 01 00 00 00 89 d9 48 d3 e0 49 09 06 eb aa be
RSP: 0018:ffffc900044eee88 EFLAGS: 00000282
RAX: 00000000044eef01 RBX: 0000000000000001 RCX: ffffc900044e8000
RDX: ffffc900044eef20 RSI: ffffc900044f0000 RDI: ffffc900044eeec0
RBP: ffff88801bb81dc0 R08: dffffc0000000001 R09: ffffc900044eef20
R10: 0000000000000000 R11: dffffc0000000001 R12: 0000000000000001
R13: 0000000000000000 R14: ffffc900044eef40 R15: 0000000000000000
__unwind_start+0x437/0x720 arch/x86/kernel/unwind_orc.c:673
unwind_start arch/x86/include/asm/unwind.h:60 [inline]
arch_stack_walk+0xdb/0x140 arch/x86/kernel/stacktrace.c:24
stack_trace_save+0x113/0x1c0 kernel/stacktrace.c:122
kasan_save_stack mm/kasan/common.c:38 [inline]
kasan_set_track+0x4b/0x80 mm/kasan/common.c:46
kasan_set_free_info+0x1f/0x40 mm/kasan/generic.c:360
____kasan_slab_free+0xd8/0x120 mm/kasan/common.c:366
kasan_slab_free include/linux/kasan.h:230 [inline]
slab_free_hook mm/slub.c:1705 [inline]
slab_free_freelist_hook+0xdd/0x160 mm/slub.c:1731
slab_free mm/slub.c:3499 [inline]
kfree+0xf1/0x270 mm/slub.c:4559
ext4_swap_extents+0xf40/0x2340 fs/ext4/extents.c:5784
move_extent_per_page+0x189c/0x2f90 fs/ext4/move_extent.c:360
ext4_move_extents+0x9a0/0xed0 fs/ext4/move_extent.c:673
__ext4_ioctl fs/ext4/ioctl.c:990 [inline]
ext4_ioctl+0x2fcb/0x5b80 fs/ext4/ioctl.c:1276
vfs_ioctl fs/ioctl.c:51 [inline]
__do_sys_ioctl fs/ioctl.c:874 [inline]
__se_sys_ioctl+0xf1/0x160 fs/ioctl.c:860
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x61/0xcb
RIP: 0033:0x7fcefe15eae9
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 e1 20 00 00 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b0 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007fcefc6e00c8 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007fcefe27df80 RCX: 00007fcefe15eae9
RDX: 0000000020000140 RSI: 00000000c028660f RDI: 0000000000000005
RBP: 00007fcefe1aa47a R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 000000000000000b R14: 00007fcefe27df80 R15: 00007ffffa870d88
</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 syzk...@googlegroups.com.

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

If the bug is already fixed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want to overwrite bug's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the bug is a duplicate of another bug, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup

syzbot

unread,
Jan 1, 2024, 12:19:17 PMJan 1
to syzkaller...@googlegroups.com
Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.
Reply all
Reply to author
Forward
0 new messages