[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZhgaXWprPHnh5LTt@casper.infradead.org>
Date: Thu, 11 Apr 2024 18:14:05 +0100
From: Matthew Wilcox <willy@...radead.org>
To: Peter Xu <peterx@...hat.com>
Cc: linux-kernel@...r.kernel.org, linux-mm@...ck.org,
Andrew Morton <akpm@...ux-foundation.org>,
Suren Baghdasaryan <surenb@...gle.com>,
Lokesh Gidra <lokeshgidra@...gle.com>,
"Liam R . Howlett" <Liam.Howlett@...cle.com>,
Alistair Popple <apopple@...dia.com>
Subject: Re: [PATCH] mm: Always sanity check anon_vma first for per-vma locks
On Thu, Apr 11, 2024 at 11:34:44AM -0400, Peter Xu wrote:
> If the answer is yes, I'd say please provide some document patch to
> support such behavior, you can stop my patch from getting merged now,
> but it's never clear whether someone else will see this and post it
> again. If it wasn't obviously to Suren who introduced per-vma lock [1],
> then I won't be surprised it's unknown to most developers on the list.
Anyone touching this path should have a good idea about what is and is
not the common case. Your confidence greatly exceeded your ability
here. I will not be submitting such a patch.
Powered by blists - more mailing lists