[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAGsJ_4zYrcooZWh0hRHqUoaiuu2eZMOuEAdGjmGArL9k925KZQ@mail.gmail.com>
Date: Mon, 4 Aug 2025 15:19:22 +0800
From: Barry Song <21cnbao@...il.com>
To: "Lai, Yi" <yi1.lai@...ux.intel.com>
Cc: akpm@...ux-foundation.org, linux-mm@...ck.org,
linux-kernel@...r.kernel.org, Barry Song <v-songbaohua@...o.com>,
Lorenzo Stoakes <lorenzo.stoakes@...cle.com>, "Liam R. Howlett" <Liam.Howlett@...cle.com>,
David Hildenbrand <david@...hat.com>, Vlastimil Babka <vbabka@...e.cz>, Jann Horn <jannh@...gle.com>,
Suren Baghdasaryan <surenb@...gle.com>, Lokesh Gidra <lokeshgidra@...gle.com>,
Tangquan Zheng <zhengtangquan@...o.com>, Qi Zheng <zhengqi.arch@...edance.com>, yi1.lai@...el.com
Subject: Re: [PATCH v4] mm: use per_vma lock for MADV_DONTNEED
On Mon, Aug 4, 2025 at 8:58 AM Lai, Yi <yi1.lai@...ux.intel.com> wrote:
>
> Hi Barry Song,
>
> Greetings!
>
> I used Syzkaller and found that there is general protection fault in __pte_offset_map_lock in linux-next next-20250801.
>
> After bisection and the first bad commit is:
> "
> a6fde7add78d mm: use per_vma lock for MADV_DONTNEED
> "
>
> All detailed into can be found at:
> https://github.com/laifryiee/syzkaller_logs/tree/main/250803_193026___pte_offset_map_lock
> Syzkaller repro code:
> https://github.com/laifryiee/syzkaller_logs/tree/main/250803_193026___pte_offset_map_lock/repro.c
Hi Lai,
Thanks for your email. I gave "repro" an initial try with today's mm-unstable
on arm64, but I wasn't able to reproduce the issue.
Please give me some time to test with your kernel and config, as well as
on x86_64 (though I'm not very familiar with x86).
Thanks
Barry
Powered by blists - more mailing lists