general protection fault in lru_add_drain_cpu

4 views
Skip to first unread message

syzbot

unread,
Jan 9, 2023, 12:03:44 PM1/9/23
to syzkaller-upst...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 41c03ba9beea Merge tag 'for_linus' of git://git.kernel.org..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=15d8da24480000
kernel config: https://syzkaller.appspot.com/x/.config?x=8cdb1e7bec4b955a
dashboard link: https://syzkaller.appspot.com/bug?extid=12e15005a6c4e485d15d
compiler: Debian clang version 13.0.1-++20220126092033+75e33f71c2da-1~exp1~20220126212112.63, GNU ld (GNU Binutils for Debian) 2.35.2
CC: [ak...@linux-foundation.org linux-...@vger.kernel.org linu...@kvack.org]

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/0785c850df02/disk-41c03ba9.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/39c091ba7dd7/vmlinux-41c03ba9.xz
kernel image: https://storage.googleapis.com/syzbot-assets/7f0500283e44/bzImage-41c03ba9.xz

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

loop1: detected capacity change from 0 to 4096
ntfs3: loop1: Different NTFS' sector size (4096) and media sector size (512)
general protection fault, probably for non-canonical address 0xfff10c17300069d1: 0000 [#1] PREEMPT SMP KASAN
KASAN: maybe wild-memory-access in range [0xff8880b980034e88-0xff8880b980034e8f]
CPU: 0 PID: 7576 Comm: syz-executor.1 Not tainted 6.2.0-rc2-syzkaller-00057-g41c03ba9beea #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/26/2022
RIP: 0010:folio_batch_count include/linux/pagevec.h:108 [inline]
RIP: 0010:lru_add_drain_cpu+0x14c/0x600 mm/swap.c:686
Code: 48 8b 5c 24 20 48 8b 44 24 38 42 80 3c 38 00 74 08 48 89 df e8 95 95 23 00 49 c7 c6 88 4e 03 00 4c 03 33 4c 89 f0 48 c1 e8 03 <42> 8a 04 38 84 c0 0f 85 9e 03 00 00 4d 8d a4 24 08 4f 03 00 41 0f
RSP: 0018:ffffc90006557200 EFLAGS: 00010a06
RAX: 1ff11017300069d1 RBX: ffffffff8cfb481f RCX: 0000000000040000
RDX: ffffc9000aba1000 RSI: 000000000001a831 RDI: 000000000001a832
RBP: ffffc90006557300 R08: dffffc0000000000 R09: ffffc90006556f20
R10: fffff52000caade9 R11: 1ffff92000caade4 R12: ffff8880b9800000
R13: 1ffff92000caae48 R14: ff8880b980034e88 R15: dffffc0000000000
FS: 00007f4b1d9e7700(0000) GS:ffff8880b9800000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000001b3162c000 CR3: 0000000035818000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
lru_add_drain+0x79/0x140 mm/swap.c:786
__pagevec_release+0x50/0xf0 mm/swap.c:1093
pagevec_release include/linux/pagevec.h:71 [inline]
folio_batch_release include/linux/pagevec.h:135 [inline]
invalidate_inode_pages2_range+0x1273/0x1520 mm/truncate.c:681
generic_file_direct_write+0x17d/0x460 mm/filemap.c:3684
__generic_file_write_iter+0x1c4/0x400 mm/filemap.c:3856
ntfs_file_write_iter+0x5ee/0x6c0 fs/ntfs3/file.c:1069
do_iter_write+0x6f0/0xc50 fs/read_write.c:861
iter_file_splice_write+0x830/0xff0 fs/splice.c:686
do_splice_from fs/splice.c:764 [inline]
direct_splice_actor+0xe6/0x1c0 fs/splice.c:931
splice_direct_to_actor+0x4e4/0xc00 fs/splice.c:886
do_splice_direct+0x2a0/0x3f0 fs/splice.c:974
do_sendfile+0x641/0xfd0 fs/read_write.c:1255
__do_sys_sendfile64 fs/read_write.c:1323 [inline]
__se_sys_sendfile64+0x178/0x1e0 fs/read_write.c:1309
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x2b/0x70 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7f4b1cc8c0c9
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 f1 19 00 00 90 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 b8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f4b1d9e7168 EFLAGS: 00000246 ORIG_RAX: 0000000000000028
RAX: ffffffffffffffda RBX: 00007f4b1cdabf80 RCX: 00007f4b1cc8c0c9
RDX: 0000000000000000 RSI: 0000000000000005 RDI: 0000000000000004
RBP: 00007f4b1cce7ae9 R08: 0000000000000000 R09: 0000000000000000
R10: 00008400fffffffa R11: 0000000000000246 R12: 0000000000000000
R13: 00007ffd915ee9ef R14: 00007f4b1d9e7300 R15: 0000000000022000
</TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:folio_batch_count include/linux/pagevec.h:108 [inline]
RIP: 0010:lru_add_drain_cpu+0x14c/0x600 mm/swap.c:686
Code: 48 8b 5c 24 20 48 8b 44 24 38 42 80 3c 38 00 74 08 48 89 df e8 95 95 23 00 49 c7 c6 88 4e 03 00 4c 03 33 4c 89 f0 48 c1 e8 03 <42> 8a 04 38 84 c0 0f 85 9e 03 00 00 4d 8d a4 24 08 4f 03 00 41 0f
RSP: 0018:ffffc90006557200 EFLAGS: 00010a06
RAX: 1ff11017300069d1 RBX: ffffffff8cfb481f RCX: 0000000000040000
RDX: ffffc9000aba1000 RSI: 000000000001a831 RDI: 000000000001a832
RBP: ffffc90006557300 R08: dffffc0000000000 R09: ffffc90006556f20
R10: fffff52000caade9 R11: 1ffff92000caade4 R12: ffff8880b9800000
R13: 1ffff92000caae48 R14: ff8880b980034e88 R15: dffffc0000000000
FS: 00007f4b1d9e7700(0000) GS:ffff8880b9800000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000001b3162c000 CR3: 0000000035818000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
----------------
Code disassembly (best guess):
0: 48 8b 5c 24 20 mov 0x20(%rsp),%rbx
5: 48 8b 44 24 38 mov 0x38(%rsp),%rax
a: 42 80 3c 38 00 cmpb $0x0,(%rax,%r15,1)
f: 74 08 je 0x19
11: 48 89 df mov %rbx,%rdi
14: e8 95 95 23 00 callq 0x2395ae
19: 49 c7 c6 88 4e 03 00 mov $0x34e88,%r14
20: 4c 03 33 add (%rbx),%r14
23: 4c 89 f0 mov %r14,%rax
26: 48 c1 e8 03 shr $0x3,%rax
* 2a: 42 8a 04 38 mov (%rax,%r15,1),%al <-- trapping instruction
2e: 84 c0 test %al,%al
30: 0f 85 9e 03 00 00 jne 0x3d4
36: 4d 8d a4 24 08 4f 03 lea 0x34f08(%r12),%r12
3d: 00
3e: 41 rex.B
3f: 0f .byte 0xf


---
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 syzk...@googlegroups.com.

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

syzbot

unread,
Apr 5, 2023, 1:00:36 PM4/5/23
to syzkaller-upst...@googlegroups.com
Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.
Reply all
Reply to author
Forward
0 new messages