From: syzbot <syzbot+d87dd8e018fd2cc2528b@syzkaller.appspotmail.com>
To: hdanton@sina.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] kernel BUG in __tlb_remove_page_size (2)
Date: Sat, 04 Feb 2023 23:40:18 -0800 [thread overview]
Message-ID: <000000000000b5e8a305f3ef06e2@google.com> (raw)
In-Reply-To: <20230205072452.1229-1-hdanton@sina.com>
Hello,
syzbot has tested the proposed patch but the reproducer is still triggering an issue:
kernel BUG in __tlb_remove_page_size
do_page_cache_ra mm/readahead.c:300 [inline]
page_cache_ra_order+0x6ec/0xa00 mm/readahead.c:560
ondemand_readahead+0x6b3/0x1080 mm/readahead.c:682
page_cache_async_ra mm/readahead.c:731 [inline]
page_cache_async_ra+0x117/0x150 mm/readahead.c:713
filemap_readahead mm/filemap.c:2572 [inline]
filemap_get_pages+0x6c5/0x16b0 mm/filemap.c:2612
filemap_read+0x315/0xc00 mm/filemap.c:2690
generic_file_read_iter+0x3ad/0x5b0 mm/filemap.c:2836
ext4_file_read_iter+0x1d9/0x690 fs/ext4/file.c:147
__kernel_read+0x2ca/0x830 fs/read_write.c:428
integrity_kernel_read+0x7f/0xb0 security/integrity/iint.c:199
ima_calc_file_hash_tfm+0x2aa/0x3b0 security/integrity/ima/ima_crypto.c:485
page_owner free stack trace missing
------------[ cut here ]------------
kernel BUG at mm/mmu_gather.c:141!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
CPU: 0 PID: 6123 Comm: rm Not tainted 6.2.0-rc6-next-20230203-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/12/2023
RIP: 0010:__tlb_remove_page_size+0x25e/0x490 mm/mmu_gather.c:141
Code: 0f 85 d3 fe ff ff e9 4b ff ff ff e8 9c 63 c1 ff 0f 0b e8 95 63 c1 ff 4c 89 f7 48 c7 c6 c0 77 58 8a 48 83 e7 fc e8 52 0b fa ff <0f> 0b e8 7b 63 c1 ff 4c 8d 6b 24 48 b8 00 00 00 00 00 fc ff df 4c
RSP: 0018:ffffc9000acef8d8 EFLAGS: 00010293
RAX: 0000000000000000 RBX: ffffc9000acefcd8 RCX: 0000000000000000
RDX: ffff88807fa50000 RSI: ffffffff81c3071e RDI: 0000000000000000
RBP: 0000000000000000 R08: 0000000000000001 R09: ffffffff8e751757
R10: fffffbfff1cea2ea R11: 0000000000000000 R12: 0000000000000001
R13: 0000000000000000 R14: ffffea0004ffbec0 R15: ffffc9000acefd00
FS: 0000000000000000(0000) GS:ffff8880b9800000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fa85e158300 CR3: 0000000027f28000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
__tlb_remove_page include/asm-generic/tlb.h:472 [inline]
zap_pte_range mm/memory.c:1416 [inline]
zap_pmd_range mm/memory.c:1536 [inline]
zap_pud_range mm/memory.c:1565 [inline]
zap_p4d_range mm/memory.c:1586 [inline]
unmap_page_range+0x1226/0x3ce0 mm/memory.c:1607
unmap_single_vma+0x194/0x2a0 mm/memory.c:1653
unmap_vmas+0x234/0x380 mm/memory.c:1692
exit_mmap+0x190/0x7d0 mm/mmap.c:3036
__mmput+0x128/0x4c0 kernel/fork.c:1209
mmput+0x60/0x70 kernel/fork.c:1231
exit_mm kernel/exit.c:563 [inline]
do_exit+0x9d7/0x2b60 kernel/exit.c:856
do_group_exit+0xd4/0x2a0 kernel/exit.c:1019
__do_sys_exit_group kernel/exit.c:1030 [inline]
__se_sys_exit_group kernel/exit.c:1028 [inline]
__x64_sys_exit_group+0x3e/0x50 kernel/exit.c:1028
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x39/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7fa85e236309
Code: Unable to access opcode bytes at 0x7fa85e2362df.
RSP: 002b:00007ffca8049e88 EFLAGS: 00000246 ORIG_RAX: 00000000000000e7
RAX: ffffffffffffffda RBX: 00007fa85e324780 RCX: 00007fa85e236309
RDX: 000000000000003c RSI: 00000000000000e7 RDI: 0000000000000000
RBP: 0000000000000000 R08: ffffffffffffff88 R09: 0000000000000001
R10: 0000000000000005 R11: 0000000000000246 R12: 00007fa85e324780
R13: 0000000000000001 R14: 00007fa85e329c88 R15: 0000000000000000
</TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:__tlb_remove_page_size+0x25e/0x490 mm/mmu_gather.c:141
Code: 0f 85 d3 fe ff ff e9 4b ff ff ff e8 9c 63 c1 ff 0f 0b e8 95 63 c1 ff 4c 89 f7 48 c7 c6 c0 77 58 8a 48 83 e7 fc e8 52 0b fa ff <0f> 0b e8 7b 63 c1 ff 4c 8d 6b 24 48 b8 00 00 00 00 00 fc ff df 4c
RSP: 0018:ffffc9000acef8d8 EFLAGS: 00010293
RAX: 0000000000000000 RBX: ffffc9000acefcd8 RCX: 0000000000000000
RDX: ffff88807fa50000 RSI: ffffffff81c3071e RDI: 0000000000000000
RBP: 0000000000000000 R08: 0000000000000001 R09: ffffffff8e751757
R10: fffffbfff1cea2ea R11: 0000000000000000 R12: 0000000000000001
R13: 0000000000000000 R14: ffffea0004ffbec0 R15: ffffc9000acefd00
FS: 0000000000000000(0000) GS:ffff8880b9800000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fa85e158300 CR3: 000000000c56f000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Tested on:
commit: 4fafd969 Add linux-next specific files for 20230203
git tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
console output: https://syzkaller.appspot.com/x/log.txt?x=10a6ec5d480000
kernel config: https://syzkaller.appspot.com/x/.config?x=1d2fba7d42502ca4
dashboard link: https://syzkaller.appspot.com/bug?extid=d87dd8e018fd2cc2528b
compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
patch: https://syzkaller.appspot.com/x/patch.diff?x=1060626b480000
next parent reply other threads:[~2023-02-05 7:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230205072452.1229-1-hdanton@sina.com>
2023-02-05 7:40 ` syzbot [this message]
[not found] <20230205094432.1510-1-hdanton@sina.com>
2023-02-05 10:33 ` [syzbot] kernel BUG in __tlb_remove_page_size (2) syzbot
[not found] <20230205082542.1363-1-hdanton@sina.com>
2023-02-05 8:53 ` syzbot
2023-02-04 13:36 syzbot
2023-02-07 14:16 ` David Howells
2023-02-07 14:31 ` syzbot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=000000000000b5e8a305f3ef06e2@google.com \
--to=syzbot+d87dd8e018fd2cc2528b@syzkaller.appspotmail.com \
--cc=hdanton@sina.com \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.