From: David Hildenbrand <david@redhat.com>
To: syzbot <syzbot+bf2c35fa302ebe3c7471@syzkaller.appspotmail.com>,
akpm@linux-foundation.org, bp@alien8.de,
dave.hansen@linux.intel.com, hpa@zytor.com, jgg@ziepe.ca,
leitao@debian.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, mingo@redhat.com, rppt@kernel.org,
syzkaller-bugs@googlegroups.com, tglx@linutronix.de,
x86@kernel.org, peterx@redhat.com
Subject: Re: [syzbot] [mm?] WARNING in copy_huge_pmd
Date: Tue, 24 Sep 2024 16:45:00 +0200 [thread overview]
Message-ID: <4f96130c-12b7-4afa-ada3-bec354576112@redhat.com> (raw)
In-Reply-To: <66f15c8d.050a0220.c23dd.000f.GAE@google.com>
On 23.09.24 14:18, syzbot wrote:
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit: 88264981f208 Merge tag 'sched_ext-for-6.12' of git://git.k..
> git tree: upstream
> console+strace: https://syzkaller.appspot.com/x/log.txt?x=16c36c27980000
> kernel config: https://syzkaller.appspot.com/x/.config?x=e851828834875d6f
> dashboard link: https://syzkaller.appspot.com/bug?extid=bf2c35fa302ebe3c7471
> compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=12773080580000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=16ed5e9f980000
>
> Downloadable assets:
> disk image: https://storage.googleapis.com/syzbot-assets/0e011ac37c93/disk-88264981.raw.xz
> vmlinux: https://storage.googleapis.com/syzbot-assets/f5c65577e19e/vmlinux-88264981.xz
> kernel image: https://storage.googleapis.com/syzbot-assets/984d963c8ea1/bzImage-88264981.xz
>
> The issue was bisected to:
>
> commit 75182022a0439788415b2dd1db3086e07aa506f7
> Author: Peter Xu <peterx@redhat.com>
> Date: Mon Aug 26 20:43:51 2024 +0000
>
> mm/x86: support large pfn mappings
>
> bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=17df9c27980000
> final oops: https://syzkaller.appspot.com/x/report.txt?x=143f9c27980000
> console output: https://syzkaller.appspot.com/x/log.txt?x=103f9c27980000
>
> IMPORTANT: if you fix the issue, please add the following tag to the commit:
> Reported-by: syzbot+bf2c35fa302ebe3c7471@syzkaller.appspotmail.com
> Fixes: 75182022a043 ("mm/x86: support large pfn mappings")
>
> ------------[ cut here ]------------
> WARNING: CPU: 1 PID: 5508 at mm/huge_memory.c:1602 copy_huge_pmd+0x102c/0x1c60 mm/huge_memory.c:1602
This is the
VM_WARN_ON_ONCE(is_cow_mapping(src_vma->vm_flags) && pmd_write(pmd))
So we have a special-marked PMD in a COW mapping.
The reproducer seems to involve fuse, but not sure if that makes a
difference here.
--
Cheers,
David / dhildenb
next prev parent reply other threads:[~2024-09-24 14:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-23 12:18 syzbot
2024-09-24 14:45 ` David Hildenbrand [this message]
2024-09-25 16:59 ` Peter Xu
2024-09-26 10:48 ` David Hildenbrand
2024-09-26 13:39 ` Peter Xu
2024-09-26 15:25 ` David Hildenbrand
2024-09-26 15:45 ` David Hildenbrand
2024-09-27 4:20 ` syzbot
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=4f96130c-12b7-4afa-ada3-bec354576112@redhat.com \
--to=david@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=jgg@ziepe.ca \
--cc=leitao@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@redhat.com \
--cc=peterx@redhat.com \
--cc=rppt@kernel.org \
--cc=syzbot+bf2c35fa302ebe3c7471@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/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