[<prev] [next>] [day] [month] [year] [list]
Message-ID: <20231116173216.GA7883@monkey>
Date: Thu, 16 Nov 2023 09:32:16 -0800
From: Mike Kravetz <mike.kravetz@...cle.com>
To: xingwei lee <xrivendell7@...il.com>
Cc: syzbot+93e7c679006f0d4e6105@...kaller.appspotmail.com,
akpm@...ux-foundation.org, linux-kernel@...r.kernel.org,
linux-mm@...ck.org, llvm@...ts.linux.dev, muchun.song@...ux.dev,
Nathan Chancellor <nathan@...nel.org>, ndesaulniers@...gle.com,
syzkaller-bugs@...glegroups.com, trix@...hat.com
Subject: Re: [syzbot] [mm?] general protection fault in hugetlb_vma_lock_read
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
Powered by blists - more mailing lists