[PATCH 3/5] riscv: mm: Fix NULL pointer dereference in __set_memory

[Michael Neuling]

On Fri, Apr 10, 2026 at 5:59 PM David Hildenbrand (Arm)
<david at kernel.org> wrote:
>
> On 4/10/26 09:53, Mike Rapoport wrote:
> > On Fri, Apr 10, 2026 at 09:42:26AM +0200, David Hildenbrand (Arm) wrote:
> >> On 4/10/26 08:23, Michael Neuling wrote:
> >>>
> >>> It wouldn't. You're right on this and the other two. Sorry for the noise.
> >>
> >> Slopped-by: Cursor:claude-4.6-opus-high-thinking
> >>
> >> :)
> >
> > It's a general tendency of LLMs to generate overly defensive code and raise
> > concerns about theoretical issues.
> > Maybe it's worth taking into account when writing prompts specific to
> > kernel development.

We've had some success using it to review some patches for maintainers.

I was attempting to use it on existing code but I agree this was
overly defensive
and didn't consider the broader context.

> Yes, and I can only urge people to actually check what the LLM spits
> out, so they won't lose their credibility with maintainers ;)

I did actually dismiss more than half of what it produced. Maybe that makes
it worse :-)

I'm not as familiar with mm so it was a mistake on my part to send these.

Mikey