[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <6e81fd7f-2208-4614-bec8-22bf4ee63147@lucifer.local>
Date: Wed, 11 Jun 2025 13:06:39 +0100
From: Lorenzo Stoakes <lorenzo.stoakes@...cle.com>
To: Jason Gunthorpe <jgg@...pe.ca>
Cc: David Hildenbrand <david@...hat.com>, John Hubbard <jhubbard@...dia.com>,
Michal Hocko <mhocko@...e.com>, linux-kernel@...r.kernel.org,
linux-mm@...ck.org, Andrew Morton <akpm@...ux-foundation.org>,
"Liam R. Howlett" <Liam.Howlett@...cle.com>,
Vlastimil Babka <vbabka@...e.cz>, Mike Rapoport <rppt@...nel.org>,
Suren Baghdasaryan <surenb@...gle.com>, Peter Xu <peterx@...hat.com>
Subject: Re: [PATCH v1] mm/gup: remove (VM_)BUG_ONs
On Wed, Jun 11, 2025 at 09:03:24AM -0300, Jason Gunthorpe wrote:
> On Wed, Jun 11, 2025 at 11:32:07AM +0200, David Hildenbrand wrote:
>
> > Later, we can do more advanced stuff, such as storing them in some other
> > buffer to persist them etc.
>
> Yeah, you should go ahead with this series, and hopefully someone will
> be inspired to separately do some work on the WARN framework..
+1 fwiw :)
Big believer in doing the practical iterative 'next step'...
If I get time + nobody else is looking at it, I'll look at doing the big churny
BUG_ON() change also!
>
> Jason
Powered by blists - more mailing lists