[syzbot] [kvm?] WARNING in srcu_check_nmi_safety (2)

[syzbot] [kvm?] WARNING in srcu_check_nmi_safety (2)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit:    abf2050f51fd Merge tag 'media/v6.12-1' of git://git.kernel..
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=114cc99f980000
kernel config:  https://syzkaller.appspot.com/x/.config?x=bc30a30374b0753
dashboard link: https://syzkaller.appspot.com/bug?extid=314c2cfd4071ad738810
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 (non-bootable): https://storage.googleapis.com/syzbot-assets/7bc7510fe41f/non_bootable_disk-abf2050f.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/2179ebeade58/vmlinux-abf2050f.xz
kernel image: https://storage.googleapis.com/syzbot-assets/f05289b5cf7c/bzImage-abf2050f.xz

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

------------[ cut here ]------------
CPU 0 old state 2 new state 1
WARNING: CPU: 0 PID: 73 at kernel/rcu/srcutree.c:708 srcu_check_nmi_safety+0xca/0x150 kernel/rcu/srcutree.c:708
Modules linked in:
CPU: 0 UID: 0 PID: 73 Comm: kswapd0 Not tainted 6.11.0-syzkaller-09959-gabf2050f51fd #0
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2~bpo12+1 04/01/2014
RIP: 0010:srcu_check_nmi_safety+0xca/0x150 kernel/rcu/srcutree.c:708
Code: 81 c3 c8 01 00 00 48 89 d8 48 c1 e8 03 42 0f b6 04 20 84 c0 75 77 8b 33 48 c7 c7 20 0c 0c 8c 89 ea 44 89 f9 e8 b7 8c db ff 90 <0f> 0b 90 90 eb 0c 42 0f b6 04 23 84 c0 75 3d 45 89 3e 48 83 c4 08
RSP: 0018:ffffc90000e464e0 EFLAGS: 00010246
RAX: 41404736cdfea900 RBX: ffffe8ffffc414c8 RCX: ffff88801efb0000
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: 0000000000000002 R08: ffffffff8155aaa2 R09: 1ffff11003f8519a
R10: dffffc0000000000 R11: ffffed1003f8519b R12: dffffc0000000000
R13: 0000607fe0041300 R14: ffffe8ffffc41320 R15: 0000000000000001
FS:  0000000000000000(0000) GS:ffff88801fc00000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000564aa6d10940 CR3: 0000000011c68000 CR4: 0000000000352ef0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <TASK>
 srcu_read_lock include/linux/srcu.h:248 [inline]
 __kvm_handle_hva_range virt/kvm/kvm_main.c:612 [inline]
 kvm_handle_hva_range virt/kvm/kvm_main.c:684 [inline]
 kvm_mmu_notifier_clear_flush_young+0xe6/0x820 virt/kvm/kvm_main.c:867
 __mmu_notifier_clear_flush_young+0x11d/0x1d0 mm/mmu_notifier.c:379
 mmu_notifier_clear_flush_young include/linux/mmu_notifier.h:410 [inline]
 folio_referenced_one+0xb9d/0x2160 mm/rmap.c:895
 rmap_walk_anon+0x4cd/0x8a0 mm/rmap.c:2638
 rmap_walk mm/rmap.c:2716 [inline]
 folio_referenced+0x394/0x7a0 mm/rmap.c:1008
 folio_check_references mm/vmscan.c:863 [inline]
 shrink_folio_list+0xe96/0x8cc0 mm/vmscan.c:1198
 evict_folios+0x549b/0x7b50 mm/vmscan.c:4583
 try_to_shrink_lruvec+0x9ab/0xbb0 mm/vmscan.c:4778
 shrink_one+0x3b9/0x850 mm/vmscan.c:4816
 shrink_many mm/vmscan.c:4879 [inline]
 lru_gen_shrink_node mm/vmscan.c:4957 [inline]
 shrink_node+0x3799/0x3de0 mm/vmscan.c:5937
 kswapd_shrink_node mm/vmscan.c:6765 [inline]
 balance_pgdat mm/vmscan.c:6957 [inline]
 kswapd+0x1ca3/0x3700 mm/vmscan.c:7226
 kthread+0x2f0/0x390 kernel/kthread.c:389
 ret_from_fork+0x4b/0x80 arch/x86/kernel/process.c:147
 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244
 </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

Re: [syzbot] [kvm?] WARNING in srcu_check_nmi_safety (2)

[Sean Christopherson]

+Kent

On Wed, Sep 25, 2024, syzbot wrote:
> Hello,
> 
> syzbot found the following issue on:
> 
> HEAD commit:    abf2050f51fd Merge tag 'media/v6.12-1' of git://git.kernel..
> git tree:       upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=114cc99f980000
> kernel config:  https://syzkaller.appspot.com/x/.config?x=bc30a30374b0753
> dashboard link: https://syzkaller.appspot.com/bug?extid=314c2cfd4071ad738810
> 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 (non-bootable): https://storage.googleapis.com/syzbot-assets/7bc7510fe41f/non_bootable_disk-abf2050f.raw.xz
> vmlinux: https://storage.googleapis.com/syzbot-assets/2179ebeade58/vmlinux-abf2050f.xz
> kernel image: https://storage.googleapis.com/syzbot-assets/f05289b5cf7c/bzImage-abf2050f.xz
> 
> IMPORTANT: if you fix the issue, please add the following tag to the commit:
> Reported-by: syzbot+314c2cfd4071ad738810@syzkaller.appspotmail.com
> 
> ------------[ cut here ]------------
> CPU 0 old state 2 new state 1
> WARNING: CPU: 0 PID: 73 at kernel/rcu/srcutree.c:708 srcu_check_nmi_safety+0xca/0x150 kernel/rcu/srcutree.c:708
> Modules linked in:
> CPU: 0 UID: 0 PID: 73 Comm: kswapd0 Not tainted 6.11.0-syzkaller-09959-gabf2050f51fd #0
> Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2~bpo12+1 04/01/2014
> RIP: 0010:srcu_check_nmi_safety+0xca/0x150 kernel/rcu/srcutree.c:708
> Code: 81 c3 c8 01 00 00 48 89 d8 48 c1 e8 03 42 0f b6 04 20 84 c0 75 77 8b 33 48 c7 c7 20 0c 0c 8c 89 ea 44 89 f9 e8 b7 8c db ff 90 <0f> 0b 90 90 eb 0c 42 0f b6 04 23 84 c0 75 3d 45 89 3e 48 83 c4 08
> RSP: 0018:ffffc90000e464e0 EFLAGS: 00010246
> RAX: 41404736cdfea900 RBX: ffffe8ffffc414c8 RCX: ffff88801efb0000
> RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
> RBP: 0000000000000002 R08: ffffffff8155aaa2 R09: 1ffff11003f8519a
> R10: dffffc0000000000 R11: ffffed1003f8519b R12: dffffc0000000000
> R13: 0000607fe0041300 R14: ffffe8ffffc41320 R15: 0000000000000001
> FS:  0000000000000000(0000) GS:ffff88801fc00000(0000) knlGS:0000000000000000
> CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> CR2: 0000564aa6d10940 CR3: 0000000011c68000 CR4: 0000000000352ef0
> DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
> DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
> Call Trace:
>  <TASK>
>  srcu_read_lock include/linux/srcu.h:248 [inline]
>  __kvm_handle_hva_range virt/kvm/kvm_main.c:612 [inline]
>  kvm_handle_hva_range virt/kvm/kvm_main.c:684 [inline]
>  kvm_mmu_notifier_clear_flush_young+0xe6/0x820 virt/kvm/kvm_main.c:867
>  __mmu_notifier_clear_flush_young+0x11d/0x1d0 mm/mmu_notifier.c:379
>  mmu_notifier_clear_flush_young include/linux/mmu_notifier.h:410 [inline]
>  folio_referenced_one+0xb9d/0x2160 mm/rmap.c:895
>  rmap_walk_anon+0x4cd/0x8a0 mm/rmap.c:2638
>  rmap_walk mm/rmap.c:2716 [inline]
>  folio_referenced+0x394/0x7a0 mm/rmap.c:1008
>  folio_check_references mm/vmscan.c:863 [inline]
>  shrink_folio_list+0xe96/0x8cc0 mm/vmscan.c:1198
>  evict_folios+0x549b/0x7b50 mm/vmscan.c:4583
>  try_to_shrink_lruvec+0x9ab/0xbb0 mm/vmscan.c:4778
>  shrink_one+0x3b9/0x850 mm/vmscan.c:4816
>  shrink_many mm/vmscan.c:4879 [inline]
>  lru_gen_shrink_node mm/vmscan.c:4957 [inline]
>  shrink_node+0x3799/0x3de0 mm/vmscan.c:5937
>  kswapd_shrink_node mm/vmscan.c:6765 [inline]
>  balance_pgdat mm/vmscan.c:6957 [inline]
>  kswapd+0x1ca3/0x3700 mm/vmscan.c:7226
>  kthread+0x2f0/0x390 kernel/kthread.c:389
>  ret_from_fork+0x4b/0x80 arch/x86/kernel/process.c:147
>  ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244
>  </TASK>

#syz set subsystems: bcachefs

Looks like another bcachefs shutdown problem.  The failure happened on a kernel
with d293ece10810 ("bcachefs: Fix shutdown ordering"), so it's not the exact same
thing as reported in https://lore.kernel.org/all/Zr-bCqSWRS3yob7V@google.com.

[   82.068524][ T5112] bcachefs (loop0): going read-write
[   82.076688][ T4530] Bluetooth: hci0: command tx timeout
[   82.092465][ T5112] bcachefs (loop0): journal_replay... done
[   82.150223][ T5112] bcachefs (loop0): resume_logged_ops... done
[   82.152607][ T5112] bcachefs (loop0): delete_dead_inodes... done
[   82.164815][ T5112] bcachefs (loop0): Fixed errors, running fsck a second time to verify fs is clean
[   82.176357][ T5112] bcachefs (loop0): resume_logged_ops... done
[   82.178950][ T5112] bcachefs (loop0): delete_dead_inodes... done
[   82.188910][ T5112] bcachefs (loop0): done starting filesystem
[   82.302896][ T5112] bcachefs (loop0): shutting down
[   82.305956][ T5112] bcachefs (loop0): going read-only
[   82.317925][ T5112] bcachefs (loop0): finished waiting for writes to stop
[   82.328724][ T5112] bcachefs (loop0): flushing journal and stopping allocators, journal seq 17
[   82.354271][ T5113] netlink: 16 bytes leftover after parsing attributes in process `syz.0.0'.
[   82.366356][ T5112] bcachefs (loop0): flushing journal and stopping allocators complete, journal seq 18
[   82.386917][ T5112] bcachefs (loop0): shutdown complete, journal seq 19
[   82.390927][ T5112] bcachefs (loop0): marking filesystem clean
[   82.472328][ T5112] bcachefs (loop0): shutdown complete
[   82.504701][   T73] ------------[ cut here ]------------
[   82.507314][   T73] CPU 0 old state 2 new state 1
[   82.509635][   T73] WARNING: CPU: 0 PID: 73 at kernel/rcu/srcutree.c:708 srcu_check_nmi_safety+0xca/0x150
[   82.513331][   T73] Modules linked in:

Re: [syzbot] [bcachefs] WARNING in srcu_check_nmi_safety (2)

[syzbot]

syzbot has found a reproducer for the following issue on:

HEAD commit:    850925a8133c Merge tag '9p-for-6.12-rc5' of https://github..
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1311ea87980000
kernel config:  https://syzkaller.appspot.com/x/.config?x=309bb816d40abc28
dashboard link: https://syzkaller.appspot.com/bug?extid=314c2cfd4071ad738810
compiler:       Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=14bf3e5f980000

Downloadable assets:
disk image (non-bootable): https://storage.googleapis.com/syzbot-assets/7feb34a89c2a/non_bootable_disk-850925a8.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/c831c931f29c/vmlinux-850925a8.xz
kernel image: https://storage.googleapis.com/syzbot-assets/85f584e52a7f/bzImage-850925a8.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/9ebb84247bd1/mount_5.gz

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

------------[ cut here ]------------
CPU 0 old state 2 new state 1
WARNING: CPU: 0 PID: 5631 at kernel/rcu/srcutree.c:708 srcu_check_nmi_safety+0xca/0x150 kernel/rcu/srcutree.c:708
Modules linked in:
CPU: 0 UID: 0 PID: 5631 Comm: syz.2.27 Not tainted 6.12.0-rc4-syzkaller-00261-g850925a8133c #0
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2~bpo12+1 04/01/2014
RIP: 0010:srcu_check_nmi_safety+0xca/0x150 kernel/rcu/srcutree.c:708
Code: 81 c3 c8 01 00 00 48 89 d8 48 c1 e8 03 42 0f b6 04 20 84 c0 75 77 8b 33 48 c7 c7 80 0d 0c 8c 89 ea 44 89 f9 e8 87 81 db ff 90 <0f> 0b 90 90 eb 0c 42 0f b6 04 23 84 c0 75 3d 45 89 3e 48 83 c4 08
RSP: 0000:ffffc9000d1c7648 EFLAGS: 00010246
RAX: 84aa6098780aa300 RBX: ffffe8ffffc537c8 RCX: ffff88803ecb8000
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: 0000000000000002 R08: ffffffff8155e452 R09: 1ffff11003f8519a
R10: dffffc0000000000 R11: ffffed1003f8519b R12: dffffc0000000000
R13: 0000607fe0053600 R14: ffffe8ffffc53620 R15: 0000000000000001
FS:  00007fe40acde6c0(0000) GS:ffff88801fc00000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fe409f7e719 CR3: 000000001f99c000 CR4: 0000000000352ef0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <TASK>
 srcu_read_lock include/linux/srcu.h:248 [inline]
 __kvm_handle_hva_range virt/kvm/kvm_main.c:612 [inline]
 kvm_mmu_notifier_invalidate_range_end+0x90/0x3e0 virt/kvm/kvm_main.c:843
 mn_hlist_invalidate_end mm/mmu_notifier.c:550 [inline]
 __mmu_notifier_invalidate_range_end+0x241/0x410 mm/mmu_notifier.c:569
 mmu_notifier_invalidate_range_end include/linux/mmu_notifier.h:472 [inline]
 wp_page_copy mm/memory.c:3460 [inline]
 do_wp_page+0x265a/0x52d0 mm/memory.c:3745
 handle_pte_fault+0x10e3/0x6800 mm/memory.c:5771
 __handle_mm_fault mm/memory.c:5898 [inline]
 handle_mm_fault+0x1106/0x1bb0 mm/memory.c:6066
 do_user_addr_fault arch/x86/mm/fault.c:1338 [inline]
 handle_page_fault arch/x86/mm/fault.c:1481 [inline]
 exc_page_fault+0x459/0x8c0 arch/x86/mm/fault.c:1539
 asm_exc_page_fault+0x26/0x30 arch/x86/include/asm/idtentry.h:623
RIP: 0033:0x7fe409e418e0
Code: 39 4f 08 72 4c 8d 4d ff 85 ed 74 33 66 0f 1f 44 00 00 48 39 f0 72 1b 4d 8b 07 49 89 c1 49 29 f1 47 0f b6 0c 08 45 84 c9 74 08 <45> 88 0c 00 49 8b 47 10 48 83 c0 01 49 89 47 10 83 e9 01 73 d3 41
RSP: 002b:00007fe40acdd4a0 EFLAGS: 00010202
RAX: 0000000000147010 RBX: 00007fe40acdd540 RCX: 0000000000000007
RDX: 00000000000007ff RSI: 0000000000001000 RDI: 00007fe40acdd5e0
RBP: 0000000000000008 R08: 00007fe400c00000 R09: 0000000000000015
R10: 0000000020005982 R11: 00000000000058ad R12: 0000000000000c01
R13: 00007fe40a005ae0 R14: 0000000000000017 R15: 00007fe40acdd5e0
 </TASK>


---
If you want syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.