All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+5250c4727db03e3436cc@syzkaller.appspotmail.com>
To: Liam.Howlett@oracle.com, akpm@linux-foundation.org,
	eadavis@qq.com,  jannh@google.com, liam.howlett@oracle.com,
	linux-kernel@vger.kernel.org,  linux-mm@kvack.org,
	lorenzo.stoakes@oracle.com, nogikh@google.com,  pfalcato@suse.de,
	syzkaller-bugs@googlegroups.com, syzkaller@googlegroups.com,
	 vbabka@suse.cz
Subject: Re: [syzbot] [mm?] general protection fault in mremap
Date: Wed, 14 May 2025 06:58:03 -0700	[thread overview]
Message-ID: <6824a16b.a70a0220.3e9d8.0015.GAE@google.com> (raw)
In-Reply-To: <67f1c7df.050a0220.0a13.0256.GAE@google.com>

syzbot suspects this issue was fixed by commit:

commit 36eed5400805b294f1df39b0e3ebc5b7971b3c16
Author: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
Date:   Sun Mar 30 16:20:48 2025 +0000

    mm/mremap: do not set vrm->vma NULL immediately prior to checking it

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=118356f4580000
start commit:   a2cc6ff5ec8f Merge tag 'firewire-updates-6.15' of git://gi..
git tree:       upstream
kernel config:  https://syzkaller.appspot.com/x/.config?x=adffebefc9feb9d6
dashboard link: https://syzkaller.appspot.com/bug?extid=5250c4727db03e3436cc
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=1693d404580000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=178ac94c580000

If the result looks correct, please mark the issue as fixed by replying with:

#syz fix: mm/mremap: do not set vrm->vma NULL immediately prior to checking it

For information about bisection process see: https://goo.gl/tpsmEJ#bisection


      parent reply	other threads:[~2025-05-14 13:58 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-06  0:16 [syzbot] [mm?] general protection fault in mremap syzbot
2025-04-06  2:02 ` Edward Adam Davis
2025-04-06  3:24   ` syzbot
2025-04-07 10:12     ` Lorenzo Stoakes
2025-04-07 10:09 ` Lorenzo Stoakes
2025-04-07 10:13   ` Aleksandr Nogikh
2025-04-07 10:28     ` Lorenzo Stoakes
2025-04-09 14:57       ` Aleksandr Nogikh
2025-04-09 17:30         ` Lorenzo Stoakes
2025-04-14 15:15           ` Aleksandr Nogikh
2025-05-14 13:58 ` syzbot [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=6824a16b.a70a0220.3e9d8.0015.GAE@google.com \
    --to=syzbot+5250c4727db03e3436cc@syzkaller.appspotmail.com \
    --cc=Liam.Howlett@oracle.com \
    --cc=akpm@linux-foundation.org \
    --cc=eadavis@qq.com \
    --cc=jannh@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=lorenzo.stoakes@oracle.com \
    --cc=nogikh@google.com \
    --cc=pfalcato@suse.de \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=syzkaller@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.