linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: David Hildenbrand <david@redhat.com>
To: syzbot <syzbot+e145145f0c83d4deb8fa@syzkaller.appspotmail.com>,
	Liam.Howlett@oracle.com, akpm@linux-foundation.org,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	lstoakes@gmail.com, syzkaller-bugs@googlegroups.com,
	vbabka@suse.cz
Subject: Re: [syzbot] [mm?] WARNING in unmap_page_range (3)
Date: Tue, 19 Mar 2024 14:32:43 +0100	[thread overview]
Message-ID: <d6eb589c-ac84-4c6f-b5f1-fdf91f3cf674@redhat.com> (raw)
In-Reply-To: <0000000000007de0cf06140124c0@google.com>

On 19.03.24 11:43, syzbot wrote:
> Hello,
> 
> syzbot found the following issue on:
> 
> HEAD commit:    e5eb28f6d1af Merge tag 'mm-nonmm-stable-2024-03-14-09-36' ..
> git tree:       upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=1383c6c9180000
> kernel config:  https://syzkaller.appspot.com/x/.config?x=4ffb854606e658d
> dashboard link: https://syzkaller.appspot.com/bug?extid=e145145f0c83d4deb8fa
> compiler:       gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
> syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=14583abe180000
> C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=14298231180000
> 
> Downloadable assets:
> disk image (non-bootable): https://storage.googleapis.com/syzbot-assets/7bc7510fe41f/non_bootable_disk-e5eb28f6.raw.xz
> vmlinux: https://storage.googleapis.com/syzbot-assets/a5c7ad05d6b2/vmlinux-e5eb28f6.xz
> kernel image: https://storage.googleapis.com/syzbot-assets/531cb1917612/bzImage-e5eb28f6.xz
> 
> IMPORTANT: if you fix the issue, please add the following tag to the commit:
> Reported-by: syzbot+e145145f0c83d4deb8fa@syzkaller.appspotmail.com
> 
> WARNING: CPU: 2 PID: 5169 at mm/memory.c:1539 zap_present_ptes mm/memory.c:1539 [inline]
> WARNING: CPU: 2 PID: 5169 at mm/memory.c:1539 zap_pte_range mm/memory.c:1603 [inline]
> WARNING: CPU: 2 PID: 5169 at mm/memory.c:1539 zap_pmd_range mm/memory.c:1720 [inline]
> WARNING: CPU: 2 PID: 5169 at mm/memory.c:1539 zap_pud_range mm/memory.c:1749 [inline]
> WARNING: CPU: 2 PID: 5169 at mm/memory.c:1539 zap_p4d_range mm/memory.c:1770 [inline]
> WARNING: CPU: 2 PID: 5169 at mm/memory.c:1539 unmap_page_range+0x2a54/0x3bf0 mm/memory.c:1791

Fix is already on its way upstream:

https://lkml.kernel.org/r/20240313213107.235067-1-peterx@redhat.com

Should shortly appear at mm-hotfixes-unstable.

#syz fix: mm/memory: Fix missing pte marker for !page on pte zaps

-- 
Cheers,

David / dhildenb



  reply	other threads:[~2024-03-19 13:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-19 10:43 [syzbot] [mm?] WARNING in unmap_page_range (3) syzbot
2024-03-19 13:32 ` David Hildenbrand [this message]
2024-06-17 13:33 ` [syzbot] " syzbot
2024-07-01 13:34 ` syzbot
2024-07-15 13:35 ` syzbot
2024-07-15 16:06   ` 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=d6eb589c-ac84-4c6f-b5f1-fdf91f3cf674@redhat.com \
    --to=david@redhat.com \
    --cc=Liam.Howlett@oracle.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=lstoakes@gmail.com \
    --cc=syzbot+e145145f0c83d4deb8fa@syzkaller.appspotmail.com \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=vbabka@suse.cz \
    /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;
as well as URLs for NNTP newsgroup(s).