linux-kernel - general protection fault in page_mkclean

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [day] [month] [year] [list]
Message-ID: <0000000000000049a305aec856c6@google.com>
Date:   Tue, 08 Sep 2020 00:32:23 -0700
From:   syzbot <syzbot+4d44c88e23baffecc385@...kaller.appspotmail.com>
To:     akpm@...ux-foundation.org, linux-kernel@...r.kernel.org,
        linux-mm@...ck.org, syzkaller-bugs@...glegroups.com
Subject: general protection fault in page_mkclean_one

Hello,

syzbot found the following issue on:

HEAD commit:    e28f0104 Merge tag 'fixes-2020-09-03' of git://git.kernel...
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1702c9e1900000
kernel config:  https://syzkaller.appspot.com/x/.config?x=3c5f6ce8d5b68299
dashboard link: https://syzkaller.appspot.com/bug?extid=4d44c88e23baffecc385
compiler:       gcc (GCC) 10.1.0-syz 20200507

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+4d44c88e23baffecc385@...kaller.appspotmail.com

general protection fault, probably for non-canonical address 0xdffffc000a02191d: 0000 [#1] PREEMPT SMP KASAN
KASAN: probably user-memory-access in range [0x000000005010c8e8-0x000000005010c8ef]
CPU: 1 PID: 8540 Comm: kworker/u4:0 Not tainted 5.9.0-rc3-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Workqueue: writeback wb_workfn (flush-8:0)
RIP: 0010:mm_has_notifiers include/linux/mmu_notifier.h:277 [inline]
RIP: 0010:mmu_notifier_invalidate_range_start include/linux/mmu_notifier.h:451 [inline]
RIP: 0010:page_mkclean_one+0x271/0x6c0 mm/rmap.c:916
Code: 89 41 b8 01 00 00 00 e8 fd b9 b1 ff 48 8b 5c 24 68 58 48 b8 00 00 00 00 00 fc ff df 48 8d bb a8 05 00 00 48 89 fa 48 c1 ea 03 <80> 3c 02 00 0f 85 f9 03 00 00 48 83 bb a8 05 00 00 00 0f 85 37 03
RSP: 0018:ffffc9001875ee60 EFLAGS: 00010206
RAX: dffffc0000000000 RBX: 000000005010c340 RCX: ffffffff815a184b
RDX: 000000000a02191d RSI: 0000000000000001 RDI: 000000005010c8e8
RBP: ffffea00017a7740 R08: 0000000000000000 R09: ffffffff8c5f49ff
R10: fffffbfff18be93f R11: 000000000000016e R12: 0000001b30823000
R13: 0000000000001000 R14: ffff88800017c420 R15: 0000000000000000
FS:  0000000000000000(0000) GS:ffff8880ae700000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000000746918 CR3: 00000002026b8000 CR4: 00000000001526e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 rmap_walk_file+0x562/0xbf0 mm/rmap.c:1928
 rmap_walk+0x105/0x190 mm/rmap.c:1946
 page_mkclean+0x21c/0x2b0 mm/rmap.c:998
 clear_page_dirty_for_io+0x31f/0x920 mm/page-writeback.c:2698
 mpage_submit_page+0x80/0x2c0 fs/ext4/inode.c:2061
 mpage_process_page_bufs+0x656/0x780 fs/ext4/inode.c:2195
 mpage_prepare_extent_to_map+0x8fa/0xde0 fs/ext4/inode.c:2607
 ext4_writepages+0x90f/0x3960 fs/ext4/inode.c:2735
 do_writepages+0xec/0x290 mm/page-writeback.c:2352
 __writeback_single_inode+0x125/0x1400 fs/fs-writeback.c:1461
 writeback_sb_inodes+0x53d/0xf40 fs/fs-writeback.c:1721
 __writeback_inodes_wb+0xc6/0x280 fs/fs-writeback.c:1790
 wb_writeback+0x8bb/0xd40 fs/fs-writeback.c:1896
 wb_check_old_data_flush fs/fs-writeback.c:1998 [inline]
 wb_do_writeback fs/fs-writeback.c:2051 [inline]
 wb_workfn+0x8f5/0x13e0 fs/fs-writeback.c:2080
 process_one_work+0x94c/0x1670 kernel/workqueue.c:2269
 worker_thread+0x64c/0x1120 kernel/workqueue.c:2415
 kthread+0x3b5/0x4a0 kernel/kthread.c:292
 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:294
Modules linked in:
---[ end trace aa72a7d82af80156 ]---
RIP: 0010:mm_has_notifiers include/linux/mmu_notifier.h:277 [inline]
RIP: 0010:mmu_notifier_invalidate_range_start include/linux/mmu_notifier.h:451 [inline]
RIP: 0010:page_mkclean_one+0x271/0x6c0 mm/rmap.c:916
Code: 89 41 b8 01 00 00 00 e8 fd b9 b1 ff 48 8b 5c 24 68 58 48 b8 00 00 00 00 00 fc ff df 48 8d bb a8 05 00 00 48 89 fa 48 c1 ea 03 <80> 3c 02 00 0f 85 f9 03 00 00 48 83 bb a8 05 00 00 00 0f 85 37 03
RSP: 0018:ffffc9001875ee60 EFLAGS: 00010206
RAX: dffffc0000000000 RBX: 000000005010c340 RCX: ffffffff815a184b
RDX: 000000000a02191d RSI: 0000000000000001 RDI: 000000005010c8e8
RBP: ffffea00017a7740 R08: 0000000000000000 R09: ffffffff8c5f49ff
R10: fffffbfff18be93f R11: 000000000000016e R12: 0000001b30823000
R13: 0000000000001000 R14: ffff88800017c420 R15: 0000000000000000
FS:  0000000000000000(0000) GS:ffff8880ae700000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fbc5e0b6d70 CR3: 00000000a3ffa000 CR4: 00000000001526e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400


---
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@...glegroups.com.

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