From: Omar Ramadan <omar@blockcast.net>
To: Paolo Abeni <pabeni@redhat.com>
Cc: netdev-bot+sinfo@kernel.org, Taehee Yoo <ap420073@gmail.com>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@kernel.org>,
Jakub Kicinski <kuba@kernel.org>, Simon Horman <horms@kernel.org>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net] amt: pull the AMT header behind the transport header in amt_parse_type()
Date: Thu, 1 Oct 2026 15:51:54 +0300 [thread overview]
Message-ID: <20261001125208.27182-1-omar@blockcast.net> (raw)
In-Reply-To: <21ba1323-7619-4721-bd1f-9ccbae42761e@redhat.com>
On Thu, Oct 1, 2026, Paolo Abeni wrote:
> Due to all the above, plus 'broken since the beginning' and Linus
> asking only for critical fixes at this point of the cycle, I'm diverting
> this one to net-next.
Thanks, Paolo, net-next is fine.
For the record, since the commit message overstates it: from reading
the code again (not reproduced), the byte read behind the quoted UDP
header stays inside the skb's head allocation, so KASAN would not
report it. The effect is a misparsed type: amt_err_lookup() counts the
error in rx_dropped instead of resending its Request at once, or
resends one it did not need to.
My reply to Eric promising a v2 with an Assisted-by: tag went to him
only, by mistake; with the patch applied there will be no v2.
next prev parent reply other threads:[~2026-10-01 12:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-28 18:15 [PATCH net] amt: pull the AMT header behind the transport header in amt_parse_type() Omar Ramadan
2026-09-28 18:20 ` netdev-bot+sinfo
2026-09-30 22:27 ` Omar Ramadan
2026-10-01 11:07 ` Paolo Abeni
2026-10-01 12:51 ` Omar Ramadan [this message]
2026-10-01 7:15 ` Eric Dumazet
2026-10-01 7:16 ` Eric Dumazet
2026-10-01 11:10 ` 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=20261001125208.27182-1-omar@blockcast.net \
--to=omar@blockcast.net \
--cc=andrew+netdev@lunn.ch \
--cc=ap420073@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev-bot+sinfo@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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.