Re: [PATCH v1] mm/gup: remove (VM_)BUG_ONs

[John Hubbard]

On 6/6/25 11:36 AM, David Hildenbrand wrote:
> On 06.06.25 20:31, John Hubbard wrote:
> > ...
> > > I think what would be *really* helpful would be quick access to the very
> > > first warning that triggered. At least that's what I usually dig 
> > > for ... :)
> >
> > These two use cases cannot be simultaneously solved, at least not
> > perfectly.
>
> I guess we'd have to store the first WARN data separately away, just 
> like when tainting the kernel or so. Not sure.

Tainting seems like a great building block. I like this idea, because
it does seem to mitigate the missing WARN_ON_ONCE(), especially if we
can capture the whole thing, backtrace and all.

thanks,
--
John Hubbard