All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+7fd4b85697bcf2a9daa2@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, hdanton@sina.com,
	linux-kernel@vger.kernel.org,  linux-mm@kvack.org,
	muchun.song@linux.dev, syzkaller-bugs@googlegroups.com,
	 usama.anjum@collabora.com, vishal.moola@gmail.com,
	willy@infradead.org
Subject: Re: [syzbot] [mm?] KASAN: slab-use-after-free Read in hugetlb_fault
Date: Mon, 10 Jun 2024 14:02:03 -0700	[thread overview]
Message-ID: <00000000000007140a061a8f7624@google.com> (raw)
In-Reply-To: <000000000000b3c7fa061652665f@google.com>

syzbot suspects this issue was fixed by commit:

commit ed74abcd1da0244c3c3be865587dc2727148ee83
Author: Muhammad Usama Anjum <usama.anjum@collabora.com>
Date:   Fri Apr 19 11:50:27 2024 +0000

    selftests: mm: protection_keys: save/restore nr_hugepages value from launch script

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=128d1bce980000
start commit:   977b1ef51866 Merge tag 'block-6.9-20240420' of git://git.k..
git tree:       upstream
kernel config:  https://syzkaller.appspot.com/x/.config?x=f47e5e015c177e57
dashboard link: https://syzkaller.appspot.com/bug?extid=7fd4b85697bcf2a9daa2
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=17c667cb180000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=149278f7180000

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

#syz fix: selftests: mm: protection_keys: save/restore nr_hugepages value from launch script

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


      parent reply	other threads:[~2024-06-10 21:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-17 22:30 [syzbot] [mm?] KASAN: slab-use-after-free Read in hugetlb_fault syzbot
2024-04-17 23:13 ` Hillf Danton
2024-04-18  2:39   ` syzbot
2024-04-18 10:49 ` Hillf Danton
2024-04-18 17:51   ` syzbot
2024-06-10 21:02 ` 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=00000000000007140a061a8f7624@google.com \
    --to=syzbot+7fd4b85697bcf2a9daa2@syzkaller.appspotmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=hdanton@sina.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=muchun.song@linux.dev \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=usama.anjum@collabora.com \
    --cc=vishal.moola@gmail.com \
    --cc=willy@infradead.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 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.