From: Jakub Kicinski <kuba@kernel.org>
To: Willem de Bruijn <willemdebruijn.kernel@gmail.com>
Cc: netdev-bot+sinfo@kernel.org, netdev@vger.kernel.org,
davem@davemloft.net, edumazet@google.com, pabeni@redhat.com,
horms@kernel.org, Chris Mason <mason@kernel.org>,
Kyle Zeng <kylebot@openai.com>,
Willem de Bruijn <willemb@google.com>
Subject: Re: [PATCH net] net: skbuff: uncharge trimmed zerocopy frags on error
Date: Tue, 10 Nov 2026 15:22:57 -0800 [thread overview]
Message-ID: <20261110152257.0e4d51cd@kernel.org> (raw)
In-Reply-To: <willemdebruijn.kernel.1d573ca061134@gmail.com>
On Thu, 05 Nov 2026 17:39:14 -0500 Willem de Bruijn 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). If it was triggered please include
> > the symptoms, like the stack trace or error messages.
>
> I thought "The issue was found by an LLM." in the commit message would be
> sufficient.
>
> This was found through analysis. A repro can be built, but its output
> only pollutes the commit message imho.
The question is whether the repro / proof was built.
Please read it again, and LMK if I should adjust the message.
next prev parent reply other threads:[~2026-11-10 23:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-05 22:35 [PATCH net] net: skbuff: uncharge trimmed zerocopy frags on error Willem de Bruijn
2026-11-05 22:37 ` netdev-bot+sinfo
2026-11-05 22:39 ` Willem de Bruijn
2026-11-10 23:22 ` Jakub Kicinski [this message]
2026-11-10 23:30 ` patchwork-bot+netdevbpf
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20261110152257.0e4d51cd@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kylebot@openai.com \
--cc=mason@kernel.org \
--cc=netdev-bot+sinfo@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=willemb@google.com \
--cc=willemdebruijn.kernel@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.