All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+ec9435c038e451be48ff@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, eadavis@qq.com,
	linux-kernel@vger.kernel.org,  linux-mm@kvack.org,
	lizhi.xu@windriver.com, llvm@lists.linux.dev,
	 mike.kravetz@oracle.com, muchun.song@linux.dev,
	nathan@kernel.org,  ndesaulniers@google.com, riel@surriel.com,
	syzkaller-bugs@googlegroups.com,  trix@redhat.com
Subject: Re: [syzbot] [mm?] general protection fault in __hugetlb_zap_begin
Date: Tue, 09 Jan 2024 10:17:07 -0800	[thread overview]
Message-ID: <0000000000007d7565060e8752d6@google.com> (raw)
In-Reply-To: <0000000000006655c10608ddfb6d@google.com>

syzbot suspects this issue was fixed by commit:

commit 187da0f8250aa94bd96266096aef6f694e0b4cd2
Author: Mike Kravetz <mike.kravetz@oracle.com>
Date:   Tue Nov 14 01:20:33 2023 +0000

    hugetlb: fix null-ptr-deref in hugetlb_vma_lock_write

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=17f5054de80000
start commit:   9b6de136b5f0 Merge tag 'loongarch-fixes-6.7-1' of git://gi..
git tree:       upstream
kernel config:  https://syzkaller.appspot.com/x/.config?x=52c9552def2a0fdd
dashboard link: https://syzkaller.appspot.com/bug?extid=ec9435c038e451be48ff
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=150a257ce80000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=13481ff0e80000

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

#syz fix: hugetlb: fix null-ptr-deref in hugetlb_vma_lock_write

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

  parent reply	other threads:[~2024-01-09 18:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-29 17:09 [syzbot] [mm?] general protection fault in __hugetlb_zap_begin syzbot
2023-11-03 11:36 ` [syzbot] [PATCH] Test for 2030579113a1 syzbot
2024-01-09 18:17 ` syzbot [this message]
     [not found] <tencent_E5C64B4991EEF2AEC68C80A7DF86E092CF06@qq.com>
2023-11-03 11:52 ` [syzbot] [mm?] general protection fault in __hugetlb_zap_begin syzbot
2023-11-03 18:12   ` Mike Kravetz

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=0000000000007d7565060e8752d6@google.com \
    --to=syzbot+ec9435c038e451be48ff@syzkaller.appspotmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=eadavis@qq.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=lizhi.xu@windriver.com \
    --cc=llvm@lists.linux.dev \
    --cc=mike.kravetz@oracle.com \
    --cc=muchun.song@linux.dev \
    --cc=nathan@kernel.org \
    --cc=ndesaulniers@google.com \
    --cc=riel@surriel.com \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=trix@redhat.com \
    /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.