From: David Hildenbrand <david@redhat.com>
To: syzbot <syzbot+273b547b15eb58ea35e8@syzkaller.appspotmail.com>,
akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] WARNING in __split_huge_page_tail
Date: Wed, 26 Oct 2022 11:54:12 +0200 [thread overview]
Message-ID: <9a450a11-531d-8e1a-4c77-70102aa7f424@redhat.com> (raw)
In-Reply-To: <000000000000aa2b2805ebea9137@google.com>
On 26.10.22 08:59, syzbot wrote:
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit: 4da34b7d175d Merge tag 'thermal-6.1-rc2' of git://git.kern..
> git tree: upstream
> console+strace: https://syzkaller.appspot.com/x/log.txt?x=113bd8bc880000
> kernel config: https://syzkaller.appspot.com/x/.config?x=4789759e8a6d5f57
> dashboard link: https://syzkaller.appspot.com/bug?extid=273b547b15eb58ea35e8
> compiler: Debian clang version 13.0.1-++20220126092033+75e33f71c2da-1~exp1~20220126212112.63, GNU ld (GNU Binutils for Debian) 2.35.2
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=161e1f62880000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=16dd4fe6880000
>
> Downloadable assets:
> disk image: https://storage.googleapis.com/syzbot-assets/a61ddb36c296/disk-4da34b7d.raw.xz
> vmlinux: https://storage.googleapis.com/syzbot-assets/ceee41246252/vmlinux-4da34b7d.xz
>
> IMPORTANT: if you fix the issue, please add the following tag to the commit:
> Reported-by: syzbot+273b547b15eb58ea35e8@syzkaller.appspotmail.com
>
> tlb_finish_mmu+0xcb/0x200 mm/mmu_gather.c:363
> exit_mmap+0x2b1/0x670 mm/mmap.c:3098
> __mmput+0x114/0x3b0 kernel/fork.c:1185
> exit_mm+0x217/0x2f0 kernel/exit.c:516
> do_exit+0x5e7/0x2070 kernel/exit.c:807
> do_group_exit+0x1fd/0x2b0 kernel/exit.c:950
> __do_sys_exit_group kernel/exit.c:961 [inline]
> __se_sys_exit_group kernel/exit.c:959 [inline]
> __x64_sys_exit_group+0x3b/0x40 kernel/exit.c:959
> 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
> ------------[ cut here ]------------
> WARNING: CPU: 0 PID: 3908 at mm/huge_memory.c:2465 __split_huge_page_tail+0x81c/0x1080 mm/huge_memory.c:2465
Is this the
VM_BUG_ON_PAGE(atomic_read(&page_tail->_mapcount) != -1, page_tail);
assertion?
--
Thanks,
David / dhildenb
next prev parent reply other threads:[~2022-10-26 9:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-26 6:59 syzbot
2022-10-26 9:54 ` David Hildenbrand [this message]
2022-10-26 13:25 ` Dmitry Vyukov
2022-10-26 14:46 ` David Hildenbrand
2022-10-26 16:17 ` Hugh Dickins
2022-11-13 16:44 ` Dmitry Vyukov
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=9a450a11-531d-8e1a-4c77-70102aa7f424@redhat.com \
--to=david@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=syzbot+273b547b15eb58ea35e8@syzkaller.appspotmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox