From: Zi Yan <ziy@nvidia.com>
To: syzbot <syzbot+012c6245eaea0e23f7f9@syzkaller.appspotmail.com>
Cc: akpm@linux-foundation.org, hughd@google.com,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [mm?] general protection fault in shmem_mapping
Date: Fri, 14 Feb 2025 13:57:12 -0500 [thread overview]
Message-ID: <D434825D-8201-4A2C-A65B-8EB8A3069B89@nvidia.com> (raw)
In-Reply-To: <67af65cb.050a0220.21dd3.004a.GAE@google.com>
On 14 Feb 2025, at 10:48, syzbot wrote:
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit: df5d6180169a Add linux-next specific files for 20250210
> git tree: linux-next
> console+strace: https://syzkaller.appspot.com/x/log.txt?x=16d343f8580000
> kernel config: https://syzkaller.appspot.com/x/.config?x=2cd616b6e736ca7
> dashboard link: https://syzkaller.appspot.com/bug?extid=012c6245eaea0e23f7f9
> 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=138972a4580000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=11737b18580000
>
> Downloadable assets:
> disk image: https://storage.googleapis.com/syzbot-assets/92495cf20271/disk-df5d6180.raw.xz
> vmlinux: https://storage.googleapis.com/syzbot-assets/4b3656161842/vmlinux-df5d6180.xz
> kernel image: https://storage.googleapis.com/syzbot-assets/7fbc4e7a0f5d/bzImage-df5d6180.xz
>
> The issue was bisected to:
>
> commit 19c067c8a0f18b62d4a4235b0b327624c86f2e40
> Author: Zi Yan <ziy@nvidia.com>
> Date: Wed Feb 5 03:14:13 2025 +0000
>
> mm/huge_memory: add buddy allocator like folio_split()
>
> bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=102f9bdf980000
> final oops: https://syzkaller.appspot.com/x/report.txt?x=122f9bdf980000
> console output: https://syzkaller.appspot.com/x/log.txt?x=142f9bdf980000
I have reproduced it locally and am working on a fix. Thanks for the reporting.
Best Regards,
Yan, Zi
next prev parent reply other threads:[~2025-02-14 18:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-14 15:48 syzbot
2025-02-14 18:57 ` Zi Yan [this message]
2025-02-14 23:26 ` Zi Yan
2025-02-14 23:26 ` syzbot
2025-02-14 23:28 ` Zi Yan
2025-02-14 23:45 ` syzbot
2025-02-15 0:48 ` Zi Yan
2025-02-15 1:15 ` 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=D434825D-8201-4A2C-A65B-8EB8A3069B89@nvidia.com \
--to=ziy@nvidia.com \
--cc=akpm@linux-foundation.org \
--cc=hughd@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=syzbot+012c6245eaea0e23f7f9@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