[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20250602175302.1115-1-sj@kernel.org>
Date: Mon, 2 Jun 2025 10:53:02 -0700
From: SeongJae Park <sj@...nel.org>
To: SeongJae Park <sj@...nel.org>
Cc: Barry Song <21cnbao@...il.com>,
Lorenzo Stoakes <lorenzo.stoakes@...cle.com>,
Jann Horn <jannh@...gle.com>,
akpm@...ux-foundation.org,
linux-mm@...ck.org,
linux-kernel@...r.kernel.org,
Barry Song <v-songbaohua@...o.com>,
"Liam R. Howlett" <Liam.Howlett@...cle.com>,
David Hildenbrand <david@...hat.com>,
Vlastimil Babka <vbabka@...e.cz>,
Suren Baghdasaryan <surenb@...gle.com>,
Lokesh Gidra <lokeshgidra@...gle.com>,
Tangquan Zheng <zhengtangquan@...o.com>
Subject: Re: [PATCH RFC v2] mm: use per_vma lock for MADV_DONTNEED
On Mon, 2 Jun 2025 10:35:19 -0700 SeongJae Park <sj@...nel.org> wrote:
> On Sat, 31 May 2025 04:17:51 +0800 Barry Song <21cnbao@...il.com> wrote:
> [...]
> > BTW, I found vector_madvise doesn't check the ret value of madvise_lock(),
> > it seems also a bug?
> >
> > static ssize_t vector_madvise(struct mm_struct *mm, struct iov_iter *iter,
> > {
> > /* Drop and reacquire lock to unwind race. */
> > madvise_finish_tlb(&madv_behavior);
> > madvise_unlock(mm, behavior);
> > madvise_lock(mm, behavior); /* missing the ret check */
> > madvise_init_tlb(&madv_behavior, mm)
> > }
>
> Thank you for finding this, I will post a fix soon.
The fix is now available at
https://lore.kernel.org/20250602174926.1074-1-sj@kernel.org
Thanks,
SJ
[...]
Powered by blists - more mailing lists