linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: David Hildenbrand <david@redhat.com>
To: syzbot <syzbot+16b1da89309a06cd0e3a@syzkaller.appspotmail.com>,
	akpm@linux-foundation.org, bhelgaas@google.com, bp@alien8.de,
	dave.hansen@linux.intel.com, guohui.study@gmail.com,
	hpa@zytor.com, jannh@google.com, kirill.shutemov@linux.intel.com,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	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, 11 Nov 2024 10:45:08 +0100	[thread overview]
Message-ID: <638e9672-850c-4bcd-bf5c-46a86be906f9@redhat.com> (raw)
In-Reply-To: <6731a6c4.050a0220.138bd5.005e.GAE@google.com>

On 11.11.24 07:40, syzbot wrote:
> syzbot has bisected this issue to:
> 
> commit 79a61cc3fc0466ad2b7b89618a6157785f0293b3
> Author: Linus Torvalds <torvalds@linux-foundation.org>
> Date:   Thu Sep 12 00:11:23 2024 +0000
> 
>      mm: avoid leaving partial pfn mappings around in error case
> 
> bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=11df65f7980000
> start commit:   7758b206117d Merge tag 'tracefs-v6.12-rc6' of git://git.ke..
> git tree:       upstream
> final oops:     https://syzkaller.appspot.com/x/report.txt?x=13df65f7980000
> console output: https://syzkaller.appspot.com/x/log.txt?x=15df65f7980000
> kernel config:  https://syzkaller.appspot.com/x/.config?x=921b01cbfd887a9b
> dashboard link: https://syzkaller.appspot.com/bug?extid=16b1da89309a06cd0e3a
> syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=148adf40580000
> C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=1704ae30580000
> 
> Reported-by: syzbot+16b1da89309a06cd0e3a@syzkaller.appspotmail.com
> Fixes: 79a61cc3fc04 ("mm: avoid leaving partial pfn mappings around in error case")
> 
> For information about bisection process see: https://goo.gl/tpsmEJ#bisection
> 

As discussed elsewhere [1], the patch [2] from Peter should fix this one.

I should probably resend both VM_PAT fixes that are on the list in a 
single series.

[1] 
https://lkml.kernel.org/r/262aa19c-59fe-420a-aeae-0b1866a3e36b@redhat.com

[2] 
https://lore.kernel.org/all/20240712144244.3090089-1-peterx@redhat.com/T/#u

-- 
Cheers,

David / dhildenb



  reply	other threads:[~2024-11-11  9:45 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
2024-11-11  9:45   ` David Hildenbrand [this message]
2025-06-30 20:06 ` syzbot
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=638e9672-850c-4bcd-bf5c-46a86be906f9@redhat.com \
    --to=david@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=bhelgaas@google.com \
    --cc=bp@alien8.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=guohui.study@gmail.com \
    --cc=hpa@zytor.com \
    --cc=jannh@google.com \
    --cc=kirill.shutemov@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=luto@kernel.org \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=seanjc@google.com \
    --cc=syzbot+16b1da89309a06cd0e3a@syzkaller.appspotmail.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