From: Jakub Kicinski <kuba@kernel.org>
To: Eric Dumazet <edumazet@kernel.org>
Cc: netdev-bot+sinfo@kernel.org,
"David S . Miller" <davem@davemloft.net>,
Paolo Abeni <pabeni@redhat.com>,
Willem de Bruijn <willemb@google.com>,
Simon Horman <horms@kernel.org>,
netdev@vger.kernel.org
Subject: Re: [PATCH net] flow_dissector: avoid u16 truncation of hlen in bpf_flow_dissect()
Date: Wed, 7 Oct 2026 17:56:41 -0700 [thread overview]
Message-ID: <20261007175641.2fb7c38b@kernel.org> (raw)
In-Reply-To: <9f688c24-488a-4862-b8fa-7a34750285c5@kernel.org>
On Wed, 7 Oct 2026 07:03:16 +0200 Eric Dumazet 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.
>
> Changelog stated: Found by sashiko while reviewing the commit above.
FWIW the AI is asking if PoC was constructed to validate that the issue
can be triggered. I spent some time polishing this message but it's far
from perfect. Not sure how to make it clear & concise :(
next prev parent reply other threads:[~2026-10-08 0:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-07 4:56 [PATCH net] flow_dissector: avoid u16 truncation of hlen in bpf_flow_dissect() Eric Dumazet
2026-10-07 5:00 ` netdev-bot+sinfo
2026-10-07 5:03 ` Eric Dumazet
2026-10-08 0:56 ` Jakub Kicinski [this message]
2026-10-08 5:34 ` Eric Dumazet
2026-10-08 2:00 ` 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=20261007175641.2fb7c38b@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=horms@kernel.org \
--cc=netdev-bot+sinfo@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=willemb@google.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.