From: syzbot <syzbot+16b1da89309a06cd0e3a@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, bhelgaas@google.com, bp@alien8.de,
dave.hansen@linux.intel.com, david@redhat.com,
guohui.study@gmail.com, hpa@zytor.com, jannh@google.com,
kirill.shutemov@linux.intel.com, liam.howlett@oracle.com,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
lorenzo.stoakes@oracle.com, luto@kernel.org, mingo@redhat.com,
peterz@infradead.org, seanjc@google.com,
syzkaller-bugs@googlegroups.com, tglx@linutronix.de,
torvalds@linux-foundation.org, x86@kernel.org
Subject: Re: [syzbot] [kernel?] WARNING in get_pat_info
Date: Mon, 30 Jun 2025 13:06:06 -0700 [thread overview]
Message-ID: <6862ee2e.a70a0220.2f4de1.002d.GAE@google.com> (raw)
In-Reply-To: <000000000000ebc1a306219068a5@google.com>
syzbot suspects this issue was fixed by commit:
commit f8e97613fed25758ddf52159b87e1c66e619a23a
Author: David Hildenbrand <david@redhat.com>
Date: Mon May 12 12:34:17 2025 +0000
mm: convert VM_PFNMAP tracking to pfnmap_track() + pfnmap_untrack()
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=12f1448c580000
start commit: fac04efc5c79 Linux 6.13-rc2
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=fee25f93665c89ac
dashboard link: https://syzkaller.appspot.com/bug?extid=16b1da89309a06cd0e3a
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=13e2ab30580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=11d113e8580000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: mm: convert VM_PFNMAP tracking to pfnmap_track() + pfnmap_untrack()
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2025-06-30 20:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <000000000000ebc1a306219068a5@google.com>
2024-11-11 6:40 ` [syzbot] [kernel?] WARNING in get_pat_info syzbot
2024-11-11 9:45 ` David Hildenbrand
2025-06-30 20:06 ` syzbot [this message]
2025-06-30 20:08 ` David Hildenbrand
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=6862ee2e.a70a0220.2f4de1.002d.GAE@google.com \
--to=syzbot+16b1da89309a06cd0e3a@syzkaller.appspotmail.com \
--cc=akpm@linux-foundation.org \
--cc=bhelgaas@google.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=david@redhat.com \
--cc=guohui.study@gmail.com \
--cc=hpa@zytor.com \
--cc=jannh@google.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=liam.howlett@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=seanjc@google.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--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