Re: [PATCH v1 net] net: Fix memory_allocated leak in __sk_mem_raise_allocated().

[Jakub Kicinski <kuba@kernel.org>]

On Thu, 5 Nov 2026 13:45:21 -0800 Kuniyuki Iwashima wrote:
> > This is an automated message. This series looks like a fix, but its
> > commit messages seem to be missing some information:
> >
> >  - Whether the issue was actually triggered, or is only theoretical
> >    (e.g. found by code inspection).  
> 
> "Found this while converting sk_memcg to obj_cgroup."

I assume you mean to imply that this sentence answers the question of
whether it was triggered, but either I'm too limited or it doesn't.
It only explains how you find the issue, which is _not_ what the bot
is asking.

> > If it was triggered please include
> >    the symptoms, like the stack trace or error messages.  
> 
> "Then, if mem_cgroup_sk_charge() succeeds, sk_prot_mem_limits()
> checks are bypassed, and if mem_cgroup_sk_charge() fails,
> sk_memory_allocated_sub() is not called, leaking counters."

"symptoms" mean dmesg basically. Please suggest better phrasing,
if you can think of it.