[syzbot] BUG: unable to handle kernel paging request in evict

[syzbot] BUG: unable to handle kernel paging request in evict

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit:    200e340f2196 Merge tag 'pull-work.dcache' of git://git.ker..
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=163e7eb6080000
kernel config:  https://syzkaller.appspot.com/x/.config?x=a3f4d6985d3164cd
dashboard link: https://syzkaller.appspot.com/bug?extid=6b74cf8fcd7378d8be7c
compiler:       gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2

Unfortunately, I don't have any reproducer for this issue yet.

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

BUG: unable to handle page fault for address: ffffffffffffffc8
#PF: supervisor write access in kernel mode
#PF: error_code(0x0002) - not-present page
PGD ba8f067 P4D ba8f067 PUD ba91067 PMD 0 
Oops: 0002 [#1] PREEMPT SMP KASAN
CPU: 0 PID: 10298 Comm: syz-executor.4 Not tainted 5.19.0-syzkaller-02972-g200e340f2196 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/22/2022
RIP: 0010:lock_acquire kernel/locking/lockdep.c:5666 [inline]
RIP: 0010:lock_acquire+0x1aa/0x570 kernel/locking/lockdep.c:5631
Code: 48 81 64 24 08 00 02 00 00 44 89 fe 6a 00 4c 89 f7 6a 00 ff b4 24 f8 00 00 00 ff 74 24 18 41 0f 94 c1 45 0f b6 c9 e8 b5 94 ff <ff> 48 c7 c7 a0 8a cc 89 48 83 c4 20 e8 25 68 19 08 b8 ff ff ff ff
RSP: 0018:ffffc90013b2f9e8 EFLAGS: 00010092
RAX: 0000000000000001 RBX: 1ffff92002765f43 RCX: ffffffff815e4bee
RDX: 1ffff11003c8b8ae RSI: 0000000000000001 RDI: ffffffff8f67d5d8
RBP: 0000000000000001 R08: 0000000000000000 R09: ffffffff9068e94f
R10: fffffbfff20d1d29 R11: 0000000000000001 R12: 0000000000000000
R13: 0000000000000000 R14: ffff88801dac49d8 R15: 0000000000000000
FS:  00007fc2d48ce700(0000) GS:ffff8880b9a00000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffffffffffffffc8 CR3: 000000002043b000 CR4: 0000000000350ef0
Call Trace:
 <TASK>
 __raw_spin_lock include/linux/spinlock_api_smp.h:133 [inline]
 _raw_spin_lock+0x2a/0x40 kernel/locking/spinlock.c:154
 spin_lock include/linux/spinlock.h:349 [inline]
 inode_sb_list_del fs/inode.c:502 [inline]
 evict+0x179/0x6b0 fs/inode.c:653
 iput_final fs/inode.c:1744 [inline]
 iput.part.0+0x562/0x820 fs/inode.c:1770
 iput+0x58/0x70 fs/inode.c:1760
 ntfs_fill_super+0x2d75/0x3750 fs/ntfs3/super.c:1180
 get_tree_bdev+0x440/0x760 fs/super.c:1292
 vfs_get_tree+0x89/0x2f0 fs/super.c:1497
 do_new_mount fs/namespace.c:3040 [inline]
 path_mount+0x1320/0x1fa0 fs/namespace.c:3370
 do_mount fs/namespace.c:3383 [inline]
 __do_sys_mount fs/namespace.c:3591 [inline]
 __se_sys_mount fs/namespace.c:3568 [inline]
 __x64_sys_mount+0x27f/0x300 fs/namespace.c:3568
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7fc2d368a73a
Code: 48 c7 c2 b8 ff ff ff f7 d8 64 89 02 b8 ff ff ff ff eb d2 e8 b8 04 00 00 0f 1f 84 00 00 00 00 00 49 89 ca b8 a5 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007fc2d48cdf88 EFLAGS: 00000206 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 0000000020000200 RCX: 00007fc2d368a73a
RDX: 0000000020000000 RSI: 0000000020000100 RDI: 00007fc2d48cdfe0
RBP: 00007fc2d48ce020 R08: 00007fc2d48ce020 R09: 0000000020000000
R10: 0000000000000000 R11: 0000000000000206 R12: 0000000020000000
R13: 0000000020000100 R14: 00007fc2d48cdfe0 R15: 000000002007aa80
 </TASK>
Modules linked in:
CR2: ffffffffffffffc8
---[ end trace 0000000000000000 ]---
RIP: 0010:lock_acquire kernel/locking/lockdep.c:5666 [inline]
RIP: 0010:lock_acquire+0x1aa/0x570 kernel/locking/lockdep.c:5631
Code: 48 81 64 24 08 00 02 00 00 44 89 fe 6a 00 4c 89 f7 6a 00 ff b4 24 f8 00 00 00 ff 74 24 18 41 0f 94 c1 45 0f b6 c9 e8 b5 94 ff <ff> 48 c7 c7 a0 8a cc 89 48 83 c4 20 e8 25 68 19 08 b8 ff ff ff ff
RSP: 0018:ffffc90013b2f9e8 EFLAGS: 00010092
RAX: 0000000000000001 RBX: 1ffff92002765f43 RCX: ffffffff815e4bee
RDX: 1ffff11003c8b8ae RSI: 0000000000000001 RDI: ffffffff8f67d5d8
RBP: 0000000000000001 R08: 0000000000000000 R09: ffffffff9068e94f
R10: fffffbfff20d1d29 R11: 0000000000000001 R12: 0000000000000000
R13: 0000000000000000 R14: ffff88801dac49d8 R15: 0000000000000000
FS:  00007fc2d48ce700(0000) GS:ffff8880b9a00000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffffffffffffffc8 CR3: 000000002043b000 CR4: 0000000000350ef0


---
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.

Re: [syzbot] BUG: unable to handle kernel paging request in evict

[syzbot]

syzbot has found a reproducer for the following issue on:

HEAD commit:    3db61221f4e8 Merge tag 'io_uring-6.0-2022-09-23' of git://..
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=120a2035080000
kernel config:  https://syzkaller.appspot.com/x/.config?x=c221af36f6d1d811
dashboard link: https://syzkaller.appspot.com/bug?extid=6b74cf8fcd7378d8be7c
compiler:       Debian clang version 13.0.1-++20220126092033+75e33f71c2da-1~exp1~20220126212112.63, GNU ld (GNU Binutils for Debian) 2.35.2
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=163d8eff080000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=159bfd60880000

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

==================================================================
BUG: KASAN: stack-out-of-bounds in native_save_fl arch/x86/include/asm/irqflags.h:35 [inline]
BUG: KASAN: stack-out-of-bounds in arch_local_save_flags arch/x86/include/asm/irqflags.h:70 [inline]
BUG: KASAN: stack-out-of-bounds in arch_irqs_disabled arch/x86/include/asm/irqflags.h:130 [inline]
BUG: KASAN: stack-out-of-bounds in lock_acquire+0x1c3/0x3c0 kernel/locking/lockdep.c:5669
Read of size 8 at addr ffffc90004dcf95f by task syz-executor479/11095

CPU: 0 PID: 11095 Comm: syz-executor479 Not tainted 6.0.0-rc6-syzkaller-00291-g3db61221f4e8 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/26/2022
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:88 [inline]
 dump_stack_lvl+0x1b1/0x28e lib/dump_stack.c:106
 print_address_description+0x65/0x4b0 mm/kasan/report.c:317
 print_report+0x108/0x1f0 mm/kasan/report.c:433
 kasan_report+0xc3/0xf0 mm/kasan/report.c:495
 native_save_fl arch/x86/include/asm/irqflags.h:35 [inline]
 arch_local_save_flags arch/x86/include/asm/irqflags.h:70 [inline]
 arch_irqs_disabled arch/x86/include/asm/irqflags.h:130 [inline]
 lock_acquire+0x1c3/0x3c0 kernel/locking/lockdep.c:5669
 __raw_spin_lock include/linux/spinlock_api_smp.h:133 [inline]
 _raw_spin_lock+0x2a/0x40 kernel/locking/spinlock.c:154
 spin_lock include/linux/spinlock.h:349 [inline]
 inode_sb_list_del fs/inode.c:503 [inline]
 evict+0x161/0x620 fs/inode.c:654
 ntfs_fill_super+0x3af3/0x42a0 fs/ntfs3/super.c:1190
 get_tree_bdev+0x400/0x620 fs/super.c:1323
 vfs_get_tree+0x88/0x270 fs/super.c:1530
 do_new_mount+0x289/0xad0 fs/namespace.c:3040
 do_mount fs/namespace.c:3383 [inline]
 __do_sys_mount fs/namespace.c:3591 [inline]
 __se_sys_mount+0x2d3/0x3c0 fs/namespace.c:3568
 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:0x7f4bae6c908a
Code: 48 c7 c2 c0 ff ff ff f7 d8 64 89 02 b8 ff ff ff ff eb d2 e8 f8 03 00 00 0f 1f 84 00 00 00 00 00 49 89 ca b8 a5 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 c0 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007ffca10c1e08 EFLAGS: 00000286 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 00007ffca10c1e60 RCX: 00007f4bae6c908a
RDX: 0000000020000000 RSI: 0000000020000100 RDI: 00007ffca10c1e20
RBP: 00007ffca10c1e20 R08: 00007ffca10c1e60 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000286 R12: 0000000020001b80
R13: 0000000000000003 R14: 0000000000000004 R15: 0000000000000110
 </TASK>

The buggy address belongs to stack of task syz-executor479/11095
 and is located at offset 31 in frame:
 lock_acquire+0x0/0x3c0 kernel/locking/lockdep.c:5621

This frame has 3 objects:
 [32, 40) 'flags.i.i.i87'
 [64, 72) 'flags.i.i.i'
 [96, 136) 'hlock'

The buggy address belongs to the virtual mapping at
 [ffffc90004dc8000, ffffc90004dd1000) created by:
 dup_task_struct+0x8b/0x490 kernel/fork.c:977

The buggy address belongs to the physical page:
page:ffffea0001d86440 refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x76191
flags: 0xfff00000000000(node=0|zone=1|lastcpupid=0x7ff)
raw: 00fff00000000000 0000000000000000 dead000000000122 0000000000000000
raw: 0000000000000000 0000000000000000 00000001ffffffff 0000000000000000
page dumped because: kasan: bad access detected
page_owner tracks the page as allocated
page last allocated via order 0, migratetype Unmovable, gfp_mask 0x2dc2(GFP_KERNEL|__GFP_HIGHMEM|__GFP_NOWARN|__GFP_ZERO), pid 3696, tgid 3696 (syz-executor479), ts 1675853778124, free_ts 1675836504134
 prep_new_page mm/page_alloc.c:2532 [inline]
 get_page_from_freelist+0x742/0x7c0 mm/page_alloc.c:4283
 __alloc_pages+0x259/0x560 mm/page_alloc.c:5515
 vm_area_alloc_pages mm/vmalloc.c:2958 [inline]
 __vmalloc_area_node mm/vmalloc.c:3026 [inline]
 __vmalloc_node_range+0x8f4/0x1290 mm/vmalloc.c:3196
 alloc_thread_stack_node+0x307/0x500 kernel/fork.c:312
 dup_task_struct+0x8b/0x490 kernel/fork.c:977
 copy_process+0x637/0x3f20 kernel/fork.c:2085
 kernel_clone+0x21f/0x790 kernel/fork.c:2671
 __do_sys_clone kernel/fork.c:2805 [inline]
 __se_sys_clone kernel/fork.c:2789 [inline]
 __x64_sys_clone+0x228/0x290 kernel/fork.c:2789
 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
page last free stack trace:
 reset_page_owner include/linux/page_owner.h:24 [inline]
 free_pages_prepare mm/page_alloc.c:1449 [inline]
 free_pcp_prepare+0x812/0x900 mm/page_alloc.c:1499
 free_unref_page_prepare mm/page_alloc.c:3380 [inline]
 free_unref_page_list+0xb4/0x7b0 mm/page_alloc.c:3522
 release_pages+0x22c3/0x2540 mm/swap.c:1012
 tlb_batch_pages_flush mm/mmu_gather.c:58 [inline]
 tlb_flush_mmu_free mm/mmu_gather.c:255 [inline]
 tlb_flush_mmu+0x850/0xa70 mm/mmu_gather.c:262
 tlb_finish_mmu+0xcb/0x200 mm/mmu_gather.c:353
 exit_mmap+0x1cb/0x520 mm/mmap.c:3118
 __mmput+0x111/0x3a0 kernel/fork.c:1187
 exit_mm+0x1ef/0x2c0 kernel/exit.c:510
 do_exit+0x4e1/0x20a0 kernel/exit.c:782
 do_group_exit+0x23b/0x2f0 kernel/exit.c:925
 __do_sys_exit_group kernel/exit.c:936 [inline]
 __se_sys_exit_group kernel/exit.c:934 [inline]
 __x64_sys_exit_group+0x3b/0x40 kernel/exit.c:934
 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

Memory state around the buggy address:
 ffffc90004dcf800: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
 ffffc90004dcf880: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>ffffc90004dcf900: 00 00 00 00 00 00 00 00 f1 f1 f1 f1 00 f2 f2 f2
                                                    ^
 ffffc90004dcf980: 00 f2 f2 f2 00 00 00 00 00 f3 f3 f3 f3 f3 f3 f3
 ffffc90004dcfa00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
==================================================================

Re: [syzbot] BUG: unable to handle kernel paging request in evict

[syzbot]

syzbot suspects this issue was fixed by commit:

commit 4e3c51f4e805291b057d12f5dda5aeb50a538dc4
Author: Svyatoslav Feldsherov <feldsherov@google.com>
Date:   Tue Nov 15 20:20:01 2022 +0000

    fs: do not update freeing inode i_io_list

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=111208cd480000
start commit:   b229b6ca5abb Merge tag 'perf-tools-fixes-for-v6.1-2022-10-..
git tree:       upstream
kernel config:  https://syzkaller.appspot.com/x/.config?x=1d3548a4365ba17d
dashboard link: https://syzkaller.appspot.com/bug?extid=6b74cf8fcd7378d8be7c
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=1353a3e2880000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=16163dce880000

If the result looks correct, please mark the issue as fixed by replying with:

#syz fix: fs: do not update freeing inode i_io_list

For information about bisection process see: https://goo.gl/tpsmEJ#bisection

Re: [syzbot] BUG: unable to handle kernel paging request in evict

[Dmitry Vyukov]

On Tue, 24 Jan 2023 at 09:57, syzbot
<syzbot+6b74cf8fcd7378d8be7c@syzkaller.appspotmail.com> wrote:
>
> syzbot suspects this issue was fixed by commit:
>
> commit 4e3c51f4e805291b057d12f5dda5aeb50a538dc4
> Author: Svyatoslav Feldsherov <feldsherov@google.com>
> Date:   Tue Nov 15 20:20:01 2022 +0000
>
>     fs: do not update freeing inode i_io_list
>
> bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=111208cd480000
> start commit:   b229b6ca5abb Merge tag 'perf-tools-fixes-for-v6.1-2022-10-..
> git tree:       upstream
> kernel config:  https://syzkaller.appspot.com/x/.config?x=1d3548a4365ba17d
> dashboard link: https://syzkaller.appspot.com/bug?extid=6b74cf8fcd7378d8be7c
> syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=1353a3e2880000
> C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=16163dce880000
>
> If the result looks correct, please mark the issue as fixed by replying with:
>
> #syz fix: fs: do not update freeing inode i_io_list
>
> For information about bisection process see: https://goo.gl/tpsmEJ#bisection

Looks reasonable. Let's close the bug report:

#syz fix: fs: do not update freeing inode i_io_list