All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+1b2ce6d050776f4403cf@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
	 linux-mm@kvack.org, syzkaller-bugs@googlegroups.com
Subject: [syzbot] [mm?] kernel BUG in folio_unlock
Date: Thu, 27 Apr 2023 08:20:51 -0700	[thread overview]
Message-ID: <000000000000e6cd7405fa52e6ad@google.com> (raw)

Hello,

syzbot found the following issue on:

HEAD commit:    d3e1ee0e67e7 Add linux-next specific files for 20230421
git tree:       linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=110654a4280000
kernel config:  https://syzkaller.appspot.com/x/.config?x=53c789efbcc06cf6
dashboard link: https://syzkaller.appspot.com/bug?extid=1b2ce6d050776f4403cf
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.

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/c558a9e1fe6a/disk-d3e1ee0e.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/2ec100a34c4c/vmlinux-d3e1ee0e.xz
kernel image: https://storage.googleapis.com/syzbot-assets/1afcd9936dc1/bzImage-d3e1ee0e.xz

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

 faultin_page mm/gup.c:925 [inline]
 __get_user_pages+0x614/0x10e0 mm/gup.c:1147
 populate_vma_page_range+0x2df/0x420 mm/gup.c:1543
 __mm_populate+0x105/0x3b0 mm/gup.c:1652
 mm_populate include/linux/mm.h:3191 [inline]
 vm_mmap_pgoff+0x2c6/0x3b0 mm/util.c:548
 ksys_mmap_pgoff+0x7d/0x5a0 mm/mmap.c:1440
 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
------------[ cut here ]------------
kernel BUG at mm/filemap.c:1529!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
CPU: 0 PID: 7377 Comm: syz-executor.1 Not tainted 6.3.0-rc7-next-20230421-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/14/2023
RIP: 0010:folio_unlock+0xb2/0xd0 mm/filemap.c:1529
Code: e8 63 4b d4 ff 48 89 ef 31 f6 e8 f9 fc ff ff 5b 5d e9 52 4b d4 ff e8 4d 4b d4 ff 48 c7 c6 c0 a7 56 8a 48 89 ef e8 ee e0 0f 00 <0f> 0b 48 89 df e8 74 2a 27 00 e9 7c ff ff ff 66 66 2e 0f 1f 84 00
RSP: 0018:ffffc9001531f7a8 EFLAGS: 00010293
RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000000
RDX: ffff88803c570000 RSI: ffffffff81af9a12 RDI: 0000000000000000
RBP: ffffea0002128000 R08: 0000000000000001 R09: ffffffff8e796e17
R10: fffffbfff1cf2dc2 R11: 0000000000000000 R12: ffffc9001531f8d8
R13: ffffc9001531f8d0 R14: ffffc9001531f8d8 R15: 000000000000001e
FS:  00007fe54afbc700(0000) GS:ffff8880b9800000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007eff0bb831b8 CR3: 0000000023ba2000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <TASK>
 collapse_file+0x1f6d/0x5db0 mm/khugepaged.c:2316
 hpage_collapse_scan_file+0xbef/0x1550 mm/khugepaged.c:2415
 madvise_collapse+0x53b/0xca0 mm/khugepaged.c:2877
 madvise_vma_behavior+0x649/0x20a0 mm/madvise.c:1074
 madvise_walk_vmas+0x1c7/0x2b0 mm/madvise.c:1248
 do_madvise.part.0+0x287/0x5e0 mm/madvise.c:1428
 do_madvise mm/madvise.c:1441 [inline]
 __do_sys_madvise mm/madvise.c:1441 [inline]
 __se_sys_madvise mm/madvise.c:1439 [inline]
 __x64_sys_madvise+0x117/0x150 mm/madvise.c:1439
 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:0x7fe54c48c169
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:00007fe54afbc168 EFLAGS: 00000246 ORIG_RAX: 000000000000001c
RAX: ffffffffffffffda RBX: 00007fe54c5ac120 RCX: 00007fe54c48c169
RDX: 0000000000000019 RSI: 000000000060005f RDI: 0000000020000000
RBP: 00007fe54c4e7ca1 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007fff8070a1ff R14: 00007fe54afbc300 R15: 0000000000022000
 </TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:folio_unlock+0xb2/0xd0 mm/filemap.c:1529
Code: e8 63 4b d4 ff 48 89 ef 31 f6 e8 f9 fc ff ff 5b 5d e9 52 4b d4 ff e8 4d 4b d4 ff 48 c7 c6 c0 a7 56 8a 48 89 ef e8 ee e0 0f 00 <0f> 0b 48 89 df e8 74 2a 27 00 e9 7c ff ff ff 66 66 2e 0f 1f 84 00
RSP: 0018:ffffc9001531f7a8 EFLAGS: 00010293
RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000000
RDX: ffff88803c570000 RSI: ffffffff81af9a12 RDI: 0000000000000000
RBP: ffffea0002128000 R08: 0000000000000001 R09: ffffffff8e796e17
R10: fffffbfff1cf2dc2 R11: 0000000000000000 R12: ffffc9001531f8d8
R13: ffffc9001531f8d0 R14: ffffc9001531f8d8 R15: 000000000000001e
FS:  00007fe54afbc700(0000) GS:ffff8880b9900000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fd2aa586058 CR3: 0000000023ba2000 CR4: 00000000003506e0
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@googlegroups.com.

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

If the bug is already fixed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want to change bug's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If you want to unassign a label, reply with:
#syz unset some-label

If the bug is a duplicate of another bug, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup


             reply	other threads:[~2023-04-27 15:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-27 15:20 syzbot [this message]
2023-04-27 20:57 ` [syzbot] [mm?] kernel BUG in folio_unlock Yang Shi

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=000000000000e6cd7405fa52e6ad@google.com \
    --to=syzbot+1b2ce6d050776f4403cf@syzkaller.appspotmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.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.