[v6.1] INFO: rcu detected stall in security_file_open

0 views
Skip to first unread message

syzbot

unread,
Sep 19, 2023, 6:15:06 PM9/19/23
to syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: a356197db198 Linux 6.1.54
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1335e8f4680000
kernel config: https://syzkaller.appspot.com/x/.config?x=86626d0659ddddaf
dashboard link: https://syzkaller.appspot.com/bug?extid=412c7bde16bb6bc57c1c
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/c61f5c33e733/disk-a356197d.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/f3643a8f0c53/vmlinux-a356197d.xz
kernel image: https://storage.googleapis.com/syzbot-assets/a3fcbc0d79f3/bzImage-a356197d.xz

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

rcu: INFO: rcu_preempt detected stalls on CPUs/tasks:
rcu: 1-...!: (0 ticks this GP) idle=2aec/1/0x4000000000000000 softirq=53916/53916 fqs=0
(detected by 0, t=10505 jiffies, g=80697, q=108 ncpus=2)
Sending NMI from CPU 0 to CPUs 1:
NMI backtrace for cpu 1
CPU: 1 PID: 3004 Comm: udevd Not tainted 6.1.54-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/04/2023
RIP: 0010:debug_deactivate+0xc3/0x280 kernel/time/hrtimer.c:483
Code: de e8 81 80 10 00 31 ff 89 de e8 78 80 10 00 40 84 ed 74 10 e8 fe 5f f9 ff 84 c0 74 1c e8 05 7e 10 00 eb 05 e8 fe 7d 10 00 5b <41> 5e 41 5f 5d c3 e8 f2 7d 10 00 0f 0b eb 95 e8 e9 7d 10 00 0f 0b
RSP: 0018:ffffc900001e0d40 EFLAGS: 00000046
RAX: ffffffff8179968b RBX: ffff8880b992a708 RCX: ffff88807bd09dc0
RDX: 0000000080010001 RSI: ffffffff8b3cea60 RDI: ffffffff8b3cea20
RBP: 0000000000000001 R08: ffffffff81799678 R09: fffffbfff1ce75e6
R10: 0000000000000000 R11: dffffc0000000001 R12: 1bc16d674ec8c3a6
R13: ffff8880b992a6c0 R14: ffff8880b992a4c0 R15: dffffc0000000000
FS: 00007f70d72f7c80(0000) GS:ffff8880b9900000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fffca74cec8 CR3: 0000000027d79000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<NMI>
</NMI>
<IRQ>
__run_hrtimer kernel/time/hrtimer.c:1653 [inline]
__hrtimer_run_queues+0x334/0xe50 kernel/time/hrtimer.c:1749
hrtimer_interrupt+0x392/0x980 kernel/time/hrtimer.c:1811
local_apic_timer_interrupt arch/x86/kernel/apic/apic.c:1095 [inline]
__sysvec_apic_timer_interrupt+0x156/0x580 arch/x86/kernel/apic/apic.c:1112
sysvec_apic_timer_interrupt+0x8c/0xb0 arch/x86/kernel/apic/apic.c:1106
</IRQ>
<TASK>
asm_sysvec_apic_timer_interrupt+0x16/0x20 arch/x86/include/asm/idtentry.h:649
RIP: 0010:kasan_quarantine_put+0x84/0x220 mm/kasan/quarantine.c:245
Code: e8 f1 00 b0 ff 48 c7 04 24 00 00 00 00 9c 8f 04 24 f7 04 24 00 02 00 00 0f 85 83 00 00 00 41 f7 c7 00 02 00 00 74 01 fb 31 c0 <48> 83 c4 08 5b 41 5c 41 5d 41 5e 41 5f c3 48 8d 80 c0 59 03 00 45
RSP: 0018:ffffc9000319f568 EFLAGS: 00000206
RAX: e8a2f8580b3e4d01 RBX: ffff88805d193c80 RCX: ffffffff91c97103
RDX: dffffc0000000000 RSI: ffffffff8aebe2a0 RDI: ffffffff8b3cea80
RBP: 0000000000000000 R08: 000000000000000d R09: 0000000000000001
R10: 0000000000000000 R11: dffffc0000000001 R12: ffff888012441640
R13: ffff88805d193c80 R14: 00000000000c71b0 R15: 0000000000000282
kasan_slab_free include/linux/kasan.h:177 [inline]
slab_free_hook mm/slub.c:1724 [inline]
slab_free_freelist_hook mm/slub.c:1750 [inline]
slab_free mm/slub.c:3661 [inline]
__kmem_cache_free+0x25c/0x3c0 mm/slub.c:3674
tomoyo_check_open_permission+0x373/0x490 security/tomoyo/file.c:786
security_file_open+0x5f/0xa0 security/security.c:1663
do_dentry_open+0x308/0x10f0 fs/open.c:869
do_open fs/namei.c:3557 [inline]
path_openat+0x2644/0x2e60 fs/namei.c:3714
do_filp_open+0x230/0x480 fs/namei.c:3741
do_sys_openat2+0x13b/0x500 fs/open.c:1318
do_sys_open fs/open.c:1334 [inline]
__do_sys_openat fs/open.c:1350 [inline]
__se_sys_openat fs/open.c:1345 [inline]
__x64_sys_openat+0x243/0x290 fs/open.c:1345
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+0x63/0xcd
RIP: 0033:0x7f70d6f1a477
Code: 10 00 00 00 44 8b 54 24 e0 48 89 44 24 c0 48 8d 44 24 d0 48 89 44 24 c8 44 89 c2 4c 89 ce bf 9c ff ff ff b8 01 01 00 00 0f 05 <48> 3d 00 f0 ff ff 76 10 48 8b 15 82 69 0d 00 f7 d8 64 89 02 48 83
RSP: 002b:00007fffbdc4faf8 EFLAGS: 00000287 ORIG_RAX: 0000000000000101
RAX: ffffffffffffffda RBX: 00005587b4390cf0 RCX: 00007f70d6f1a477
RDX: 0000000000090800 RSI: 00005587b437a020 RDI: 00000000ffffff9c
RBP: 00005587b4445170 R08: 0000000000090800 R09: 00005587b437a020
R10: 0000000000000000 R11: 0000000000000287 R12: 00005587b437a020
R13: 00000000000000ff R14: 00005587b41701c4 R15: 0000000000000000
</TASK>
rcu: rcu_preempt kthread timer wakeup didn't happen for 10504 jiffies! g80697 f0x0 RCU_GP_WAIT_FQS(5) ->state=0x402
rcu: Possible timer handling issue on cpu=1 timer-softirq=74311
rcu: rcu_preempt kthread starved for 10505 jiffies! g80697 f0x0 RCU_GP_WAIT_FQS(5) ->state=0x402 ->cpu=1
rcu: Unless rcu_preempt kthread gets sufficient CPU time, OOM is now expected behavior.
rcu: RCU grace-period kthread stack dump:
task:rcu_preempt state:I stack:26680 pid:16 ppid:2 flags:0x00004000
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5241 [inline]
__schedule+0x132c/0x4330 kernel/sched/core.c:6554
schedule+0xbf/0x180 kernel/sched/core.c:6630
schedule_timeout+0x1b9/0x300 kernel/time/timer.c:1935
rcu_gp_fqs_loop+0x2c2/0x1010 kernel/rcu/tree.c:1661
rcu_gp_kthread+0xa3/0x3a0 kernel/rcu/tree.c:1860
kthread+0x26e/0x300 kernel/kthread.c:376
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:306
</TASK>
rcu: Stack dump where RCU GP kthread last ran:
Sending NMI from CPU 0 to CPUs 1:
NMI backtrace for cpu 1
CPU: 1 PID: 3004 Comm: udevd Not tainted 6.1.54-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/04/2023
RIP: 0010:timerqueue_del+0xb7/0xf0 lib/timerqueue.c:58
Code: 89 df 49 89 c7 e8 59 6d 60 f7 4c 89 f8 48 89 03 4c 89 ef 4c 89 f6 e8 a8 71 ff ff 41 80 3c 2c 00 74 08 4c 89 ef e8 39 6d 60 f7 <4d> 89 6d 00 4c 89 f0 48 c1 e8 03 80 3c 28 00 74 08 4c 89 f7 e8 a0
RSP: 0018:ffffc900001e0d28 EFLAGS: 00000046
RAX: 1ffff110173254e2 RBX: ffff8880b992a718 RCX: dffffc0000000000
RDX: 0000000080010001 RSI: ffff8880b992a710 RDI: ffff88808b725348
RBP: dffffc0000000000 R08: ffffffff8a805774 R09: fffffbfff1ce75e6
R10: 0000000000000000 R11: dffffc0000000001 R12: 1ffff110116e4a68
R13: ffff88808b725340 R14: ffff8880b992a710 R15: 1ffff110173254e3
FS: 00007f70d72f7c80(0000) GS:ffff8880b9900000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fffca74cec8 CR3: 0000000027d79000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<NMI>
</NMI>
<IRQ>
__remove_hrtimer kernel/time/hrtimer.c:1116 [inline]
__run_hrtimer kernel/time/hrtimer.c:1665 [inline]
__hrtimer_run_queues+0x409/0xe50 kernel/time/hrtimer.c:1749
hrtimer_interrupt+0x392/0x980 kernel/time/hrtimer.c:1811
local_apic_timer_interrupt arch/x86/kernel/apic/apic.c:1095 [inline]
__sysvec_apic_timer_interrupt+0x156/0x580 arch/x86/kernel/apic/apic.c:1112
sysvec_apic_timer_interrupt+0x8c/0xb0 arch/x86/kernel/apic/apic.c:1106
</IRQ>
<TASK>
asm_sysvec_apic_timer_interrupt+0x16/0x20 arch/x86/include/asm/idtentry.h:649
RIP: 0010:kasan_quarantine_put+0x84/0x220 mm/kasan/quarantine.c:245
Code: e8 f1 00 b0 ff 48 c7 04 24 00 00 00 00 9c 8f 04 24 f7 04 24 00 02 00 00 0f 85 83 00 00 00 41 f7 c7 00 02 00 00 74 01 fb 31 c0 <48> 83 c4 08 5b 41 5c 41 5d 41 5e 41 5f c3 48 8d 80 c0 59 03 00 45
RSP: 0018:ffffc9000319f568 EFLAGS: 00000206
RAX: e8a2f8580b3e4d01 RBX: ffff88805d193c80 RCX: ffffffff91c97103
RDX: dffffc0000000000 RSI: ffffffff8aebe2a0 RDI: ffffffff8b3cea80
RBP: 0000000000000000 R08: 000000000000000d R09: 0000000000000001
R10: 0000000000000000 R11: dffffc0000000001 R12: ffff888012441640
R13: ffff88805d193c80 R14: 00000000000c71b0 R15: 0000000000000282
kasan_slab_free include/linux/kasan.h:177 [inline]
slab_free_hook mm/slub.c:1724 [inline]
slab_free_freelist_hook mm/slub.c:1750 [inline]
slab_free mm/slub.c:3661 [inline]
__kmem_cache_free+0x25c/0x3c0 mm/slub.c:3674
tomoyo_check_open_permission+0x373/0x490 security/tomoyo/file.c:786
security_file_open+0x5f/0xa0 security/security.c:1663
do_dentry_open+0x308/0x10f0 fs/open.c:869
do_open fs/namei.c:3557 [inline]
path_openat+0x2644/0x2e60 fs/namei.c:3714
do_filp_open+0x230/0x480 fs/namei.c:3741
do_sys_openat2+0x13b/0x500 fs/open.c:1318
do_sys_open fs/open.c:1334 [inline]
__do_sys_openat fs/open.c:1350 [inline]
__se_sys_openat fs/open.c:1345 [inline]
__x64_sys_openat+0x243/0x290 fs/open.c:1345
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+0x63/0xcd
RIP: 0033:0x7f70d6f1a477
Code: 10 00 00 00 44 8b 54 24 e0 48 89 44 24 c0 48 8d 44 24 d0 48 89 44 24 c8 44 89 c2 4c 89 ce bf 9c ff ff ff b8 01 01 00 00 0f 05 <48> 3d 00 f0 ff ff 76 10 48 8b 15 82 69 0d 00 f7 d8 64 89 02 48 83
RSP: 002b:00007fffbdc4faf8 EFLAGS: 00000287 ORIG_RAX: 0000000000000101
RAX: ffffffffffffffda RBX: 00005587b4390cf0 RCX: 00007f70d6f1a477
RDX: 0000000000090800 RSI: 00005587b437a020 RDI: 00000000ffffff9c
RBP: 00005587b4445170 R08: 0000000000090800 R09: 00005587b437a020
R10: 0000000000000000 R11: 0000000000000287 R12: 00005587b437a020
R13: 00000000000000ff R14: 00005587b41701c4 R15: 0000000000000000
</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,
Dec 28, 2023, 5:15:15 PM12/28/23
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