Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
MIME-Version: 1.0
Date:   Tue, 23 Aug 2022 18:02:34 -0700
Message-ID: <0000000000007d901905e6f23c23@google.com>
Subject: [syzbot] WARNING: CPU: NUM PID: NUM at mm/huge_memory.c:LINE split_huge_page_to_l
From:   syzbot <syzbot+2184d61af7d9d86337fc@syzkaller.appspotmail.com>
To:     akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
        linux-mm@kvack.org, syzkaller-bugs@googlegroups.com
Content-Type: text/plain; charset="UTF-8"
Precedence: bulk

Hello,

syzbot found the following issue on:

HEAD commit:    680fb5b009e8 Merge tag 'arm64-upstream' into for-kernelci
git tree:       git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci
console output: https://syzkaller.appspot.com/x/log.txt?x=13d186a5080000
kernel config:  https://syzkaller.appspot.com/x/.config?x=4557ad2600fc45f4
dashboard link: https://syzkaller.appspot.com/bug?extid=2184d61af7d9d86337fc
compiler:       Debian clang version 13.0.1-++20220126092033+75e33f71c2da-1~exp1~20220126212112.63, GNU ld (GNU Binutils for Debian) 2.35.2
userspace arch: arm64
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=13c0bffd080000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=1217ce8d080000

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

raw: 05ffc00000010801 0000000000000000 dead000000000122 0000000000000000
raw: 0000000000000000 0000000000000000 00000002ffffffff 0000000000000000
page dumped because: VM_WARN_ON_ONCE_PAGE(is_hzp)
------------[ cut here ]------------
WARNING: CPU: 0 PID: 3026 at mm/huge_memory.c:2555 split_huge_page_to_l


---
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.
syzbot can test patches for this issue, for details see:
https://goo.gl/tpsmEJ#testing-patches