From: "Lorenzo Stoakes (Oracle)" <ljs@kernel.org>
To: Mike Rapoport <rppt@kernel.org>
Cc: syzbot <syzbot+de14f7701c22477db718@syzkaller.appspotmail.com>,
Liam.Howlett@oracle.com, akpm@linux-foundation.org,
baohua@kernel.org, baolin.wang@linux.alibaba.com,
david@kernel.org, dev.jain@arm.com, lance.yang@linux.dev,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
npache@redhat.com, ryan.roberts@arm.com,
syzkaller-bugs@googlegroups.com, ziy@nvidia.com,
Harry Yoo <harry.yoo@oracle.com>
Subject: Re: [syzbot] [mm?] general protection fault in zap_huge_pmd
Date: Thu, 19 Mar 2026 08:54:45 +0000 [thread overview]
Message-ID: <2355172e-d696-47e5-839e-16f1ae5373ba@lucifer.local> (raw)
In-Reply-To: <abuNkfv8c1IrGk0E@kernel.org>
On Thu, Mar 19, 2026 at 07:45:53AM +0200, Mike Rapoport wrote:
> On Wed, Mar 18, 2026 at 05:26:32PM +0000, Lorenzo Stoakes (Oracle) wrote:
> > +cc Mike for uffd, Harry for fix that also resolves this, see below
> >
> > On Wed, Mar 18, 2026 at 08:03:22AM -0700, syzbot wrote:
> > > Hello,
> > >
> > > syzbot found the following issue on:
> > >
> > > HEAD commit: b84a0ebe421c Add linux-next specific files for 20260313
> >
> > For some reason I have to git pull --tags to get this... commit hash locally?
> > Strange.
> >
> > > git tree: linux-next
> > > console output: https://syzkaller.appspot.com/x/log.txt?x=119ddd52580000
> > > kernel config: https://syzkaller.appspot.com/x/.config?x=e7280ad1f68b2dce
> > > dashboard link: https://syzkaller.appspot.com/bug?extid=de14f7701c22477db718
> > > compiler: Debian clang version 21.1.8 (++20251221033036+2078da43e25a-1~exp1~20251221153213.50), Debian LLD 21.1.8
> > > syz repro: https://syzkaller.appspot.com/x/repro.syz?x=173b44da580000
> > > C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1537b8da580000
> >
> > @SYZKALLER guys:
> >
> > Note: the repro is incorrectly labelling;
> >
> > // ioctl$UFFDIO_CONTINUE arguments: [
> > // fd: fd_uffd (resource)
> > // cmd: const = 0xc020aa08 (4 bytes)
> >
> > as UFFDIO_CONTINUE (0x7), it's actually UFFDIO_POISION (0x8) as you can see
> > from least-significant byte.
> >
> > It's also stating things like mmap flags wrong e.g.:
> >
> > /*flags=MAP_UNINITIALIZED|MAP_POPULATE|MAP_NORESERVE|MAP_NONBLOCK|MAP_HUGETLB|0x8c4b815a506002b2*/
> > 0x8c4b815a5465c2b2ul,
>
> As Andrey Vagin pointed off-list, you can run strace repro and see the
> syscall arguments quite nicely :-)
Yeah, but we really shouldn't need to have to :)
>
> > So Harry's fix resolves this,
>
> and that's the important bit ;-P
Yep
>
> > but we should handle this case better in zap_huge_pmd(), I will send a
> > patch for that.
And already did this ^ :)
>
> > Cheers, Lorenzo
>
> --
> Sincerely yours,
> Mike.
Cheers, Lorenzo
prev parent reply other threads:[~2026-03-19 8:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-18 15:03 syzbot
2026-03-18 16:53 ` Lance Yang
2026-03-18 17:35 ` Lorenzo Stoakes (Oracle)
2026-03-19 2:58 ` Lance Yang
2026-03-18 17:26 ` Lorenzo Stoakes (Oracle)
2026-03-18 21:54 ` Aleksandr Nogikh
2026-03-19 10:04 ` Lorenzo Stoakes (Oracle)
2026-03-19 3:09 ` Lance Yang
2026-03-19 5:45 ` Mike Rapoport
2026-03-19 8:54 ` Lorenzo Stoakes (Oracle) [this message]
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=2355172e-d696-47e5-839e-16f1ae5373ba@lucifer.local \
--to=ljs@kernel.org \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=baohua@kernel.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=david@kernel.org \
--cc=dev.jain@arm.com \
--cc=harry.yoo@oracle.com \
--cc=lance.yang@linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=npache@redhat.com \
--cc=rppt@kernel.org \
--cc=ryan.roberts@arm.com \
--cc=syzbot+de14f7701c22477db718@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=ziy@nvidia.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