From: Kamil Sawicki <user148783812897@gmail.com>
To: netdev@vger.kernel.org
Subject: Re: [PATCH net] net: limit priority VLAN untag depth
Date: Thu, 22 Oct 2026 20:57:41 -0400 [thread overview]
Message-ID: <20261023005742.1144360-1-user148783812897@gmail.com> (raw)
In-Reply-To: <20261023003750.1133904-1-user148783812897@gmail.com>
Hi,
I discovered this issue while researching the Linux network receive path for
Google kvmCTF, with OpenAI Codex (gpt-5.6-sol) assisting the code analysis.
I manually reviewed the affected path, reproduced the issue through
vhost-net/TAP on Linux 6.1.74 and current net/main, and validated the fix with
differential KASAN, ftrace, boundary, GSO and BIG TCP tests. The existing
Assisted-by tag records the model used.
Thanks,
Kamil
next prev parent reply other threads:[~2026-10-23 0:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-23 0:37 [PATCH net] net: limit priority VLAN untag depth Kamil Sawicki
2026-10-23 0:42 ` netdev-bot+sinfo
2026-10-23 0:57 ` Kamil Sawicki [this message]
2026-10-23 1:40 ` Willem de Bruijn
2026-10-27 0:40 ` netdev-bot+sashiko
2026-10-27 1:39 ` Kuniyuki Iwashima
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=20261023005742.1144360-1-user148783812897@gmail.com \
--to=user148783812897@gmail.com \
--cc=netdev@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox