From: Mike Kravetz <mike.kravetz@oracle.com>
To: xingwei lee <xrivendell7@gmail.com>
Cc: syzbot+93e7c679006f0d4e6105@syzkaller.appspotmail.com,
akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, llvm@lists.linux.dev, muchun.song@linux.dev,
Nathan Chancellor <nathan@kernel.org>,
ndesaulniers@google.com, syzkaller-bugs@googlegroups.com,
trix@redhat.com
Subject: Re: [syzbot] [mm?] general protection fault in hugetlb_vma_lock_read
Date: Thu, 16 Nov 2023 09:32:16 -0800 [thread overview]
Message-ID: <20231116173216.GA7883@monkey> (raw)
In-Reply-To: <CABOYnLzpDMPd3fJhi38N_jcQS6ZSa8RNik5j_APKQYNk0kJRkw@mail.gmail.com>
On 11/16/23 15:53, xingwei lee wrote:
> Hello, since I found there is no reproduce from then to now. I try to
> reproduce this bug to generate repro.c.
> Maybe this bug is the same bug as [syzbot] [mm?] general protection fault
> in hugetlb_vma_lock_write I guess...
> But no matter what, with the reproduce.c, we can quickly fix this bug or
> check the correctness of our fix.
I am not sure what fix you suggested for this issue. The following was
sent upstream and is now included in Andrew's tree and linux-next.
https://lore.kernel.org/linux-mm/20231114012033.259600-1-mike.kravetz@oracle.com/
I tested with a reproducer previously provided by syzbot, and assume this
resolves the issue with your reproducer as well.
--
Mike Kravetz
next prev parent reply other threads:[~2023-11-16 17:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-16 7:53 [syzbot] [mm?] general protection fault in hugetlb_vma_lock_read xingwei lee
2023-11-16 17:32 ` Mike Kravetz [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-11-02 15:26 syzbot
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=20231116173216.GA7883@monkey \
--to=mike.kravetz@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=llvm@lists.linux.dev \
--cc=muchun.song@linux.dev \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=syzbot+93e7c679006f0d4e6105@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=trix@redhat.com \
--cc=xrivendell7@gmail.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.