[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <67436e63.050a0220.1cc393.0048.GAE@google.com>
Date: Sun, 24 Nov 2024 10:20:19 -0800
From: syzbot <syzbot+2f32bc207cbe5ca4b7a2@...kaller.appspotmail.com>
To: bp@...en8.de, dave.hansen@...ux.intel.com, hpa@...or.com,
linux-kernel@...r.kernel.org, luto@...nel.org, mingo@...hat.com,
peterz@...radead.org, syzkaller-bugs@...glegroups.com, tglx@...utronix.de,
x86@...nel.org
Subject: [syzbot] [kernel?] WARNING in flush_tlb_func
Hello,
syzbot found the following issue on:
HEAD commit: ac24e26aa08f Add linux-next specific files for 20241120
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=136a1930580000
kernel config: https://syzkaller.appspot.com/x/.config?x=45719eec4c74e6ba
dashboard link: https://syzkaller.appspot.com/bug?extid=2f32bc207cbe5ca4b7a2
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/9c6bcf3605c7/disk-ac24e26a.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/4ce96eb398a9/vmlinux-ac24e26a.xz
kernel image: https://storage.googleapis.com/syzbot-assets/9a22aac22c90/bzImage-ac24e26a.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+2f32bc207cbe5ca4b7a2@...kaller.appspotmail.com
------------[ cut here ]------------
WARNING: CPU: 0 PID: 5987 at arch/x86/mm/tlb.c:816 flush_tlb_func+0x631/0x700 arch/x86/mm/tlb.c:816
Modules linked in:
CPU: 0 UID: 0 PID: 5987 Comm: syz.4.29 Not tainted 6.12.0-next-20241120-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/30/2024
RIP: 0010:flush_tlb_func+0x631/0x700 arch/x86/mm/tlb.c:816
Code: e9 16 fb ff ff 90 0f 0b 90 e9 76 fb ff ff 45 31 f6 49 bc 00 00 00 00 00 fc ff df e9 53 ff ff ff 90 0f 0b 90 e9 8f fc ff ff 90 <0f> 0b 90 e9 a8 fc ff ff 90 0f 0b 90 e9 d5 fb ff ff 90 0f 0b 90 e9
RSP: 0018:ffffc900044fea20 EFLAGS: 00010016
RAX: dffffc0000000000 RBX: ffff8880b863d7c0 RCX: dffffc0000000000
RDX: 0000000000000000 RSI: 0000000000000008 RDI: ffff8880290b9a88
RBP: ffffc900044feb10 R08: ffff8880290b9a8f R09: 1ffff11005217351
R10: dffffc0000000000 R11: ffffed1005217352 R12: 1ffff110170c7afb
R13: 000000000000001a R14: 0000000000000019 R15: ffff8880b863d7d8
FS: 00007fcd5b0116c0(0000) GS:ffff8880b8600000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f8e8dc656c0 CR3: 000000005fae2000 CR4: 00000000003526f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
csd_do_func kernel/smp.c:134 [inline]
smp_call_function_many_cond+0x1760/0x2ca0 kernel/smp.c:875
on_each_cpu_cond_mask+0x3f/0x80 kernel/smp.c:1051
__flush_tlb_multi arch/x86/include/asm/paravirt.h:91 [inline]
flush_tlb_multi arch/x86/mm/tlb.c:938 [inline]
flush_tlb_mm_range+0x329/0x5c0 arch/x86/mm/tlb.c:1024
flush_tlb_page arch/x86/include/asm/tlbflush.h:254 [inline]
ptep_clear_flush+0x11a/0x170 mm/pgtable-generic.c:101
page_vma_mkclean_one+0x58a/0x9a0 mm/rmap.c:1051
page_mkclean_one+0x280/0x420 mm/rmap.c:1092
rmap_walk_file+0x52f/0x9f0 mm/rmap.c:2708
rmap_walk mm/rmap.c:2726 [inline]
folio_mkclean+0x262/0x440 mm/rmap.c:1124
folio_clear_dirty_for_io+0x22b/0xd00 mm/page-writeback.c:3033
mpage_submit_folio+0x88/0x230 fs/ext4/inode.c:1913
mpage_map_and_submit_buffers fs/ext4/inode.c:2178 [inline]
mpage_map_and_submit_extent fs/ext4/inode.c:2310 [inline]
ext4_do_writepages+0x1d15/0x3d10 fs/ext4/inode.c:2735
ext4_writepages+0x213/0x3c0 fs/ext4/inode.c:2824
do_writepages+0x35f/0x880 mm/page-writeback.c:2702
filemap_fdatawrite_wbc mm/filemap.c:397 [inline]
__filemap_fdatawrite_range mm/filemap.c:430 [inline]
file_write_and_wait_range+0x2a3/0x3c0 mm/filemap.c:787
ext4_sync_file+0x25d/0xb90 fs/ext4/fsync.c:158
__do_sys_msync mm/msync.c:96 [inline]
__se_sys_msync+0x3d7/0x5a0 mm/msync.c:32
do_syscall_x64 arch/x86/entry/common.c:52 [inline]
do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7fcd5a17e819
Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 a8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007fcd5b011038 EFLAGS: 00000246 ORIG_RAX: 000000000000001a
RAX: ffffffffffffffda RBX: 00007fcd5a335fa0 RCX: 00007fcd5a17e819
RDX: 0000000000000004 RSI: 087abbe8d1cc6ad9 RDI: 0000000020952000
RBP: 00007fcd5a1f175e R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000000 R14: 00007fcd5a335fa0 R15: 00007ffc671020c8
</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@...glegroups.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
Powered by blists - more mailing lists