From: netdev-bot+sashiko@kernel.org
To: omar@blockcast.net
Cc: ap420073@gmail.com, andrew+netdev@lunn.ch, davem@davemloft.net,
edumazet@kernel.org, kuba@kernel.org, pabeni@redhat.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
horms@kernel.org, bigeasy@linutronix.de, clrkwllms@kernel.org,
rostedt@goodmis.org, linux-rt-devel@lists.linux.dev
Subject: Re: [PATCH net v5 4/5] amt: make pre-query report drops visible
Date: Mon, 09 Nov 2026 14:49:19 +0000 [thread overview]
Message-ID: <179423575970.994134.5432026388018419992@kernel.org> (raw)
In-Reply-To: <20261105125010.1107546-5-omar@blockcast.net>
Thank you for your contribution! Sashiko AI review found more severe
issue(s) in other patches of this series. This mail is only an FYI, in case
you want to address the nit picks below when you respin.
Low priority / nit picks for your consideration:
- [Low] The commit message says DEV_STATS_INC() is applied only to
amt_dev_xmit()'s counters: "The device is LLTX, so amt_dev_xmit() can…
--
amt: make pre-query report drops visible
This patch adds a debug message when an amt gateway drops an IGMP or MLD
report because the relay's Membership Query has not arrived yet. It also
stops amt_dev_xmit() from counting reports it forwarded as tx_dropped.
Finally, it switches the device's tx_dropped and tx_errors updates to
DEV_STATS_INC().
> The device is LLTX, so amt_dev_xmit() can run on several CPUs at once;
> use DEV_STATS_INC() for its tx_dropped and tx_errors updates so
> concurrent increments are not lost.
[Severity: Low]
This isn't a bug, but does this paragraph cover the whole diff?
It describes the DEV_STATS_INC() change as limited to amt_dev_xmit().
Only two of the converted sites are in that function. The patch also
converts every other tx_errors and tx_dropped increment in
drivers/net/amt.c:
amt_send_discovery() (three tx_errors sites)
amt_send_request() (three tx_errors sites)
amt_send_igmp_gq() (tx_dropped)
amt_build_mld_gq() (tx_errors)
amt_send_mld_gq() (tx_dropped)
amt_send_advertisement() (three tx_errors sites)
These run from the gateway workqueue and the relay receive path, not
from ndo_start_xmit.
The extra conversions look correct and are needed. DEV_STATS_INC() does
atomic_long_inc() on the same storage as dev->stats.tx_errors and
dev->stats.tx_dropped. A plain ++ left on either field could overwrite
an atomic increment from amt_dev_xmit().
Could the commit message mention these conversions and give that reason?
--
Sashiko AI review · https://netdev-ai.bots.linux.dev/sashiko/#/patchset/20261105125010.1107546-1-omar%40blockcast.net
next prev parent reply other threads:[~2026-11-09 14:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-05 12:50 [PATCH net v5 0/5] amt: relay tunnel lifetime, validation and request-path hardening Omar Ramadan
2026-11-05 12:50 ` [PATCH net v5 1/5] amt: fix use-after-free when a Membership Update re-arms a freed tunnel Omar Ramadan
2026-11-06 12:50 ` sashiko-bot
2026-11-09 14:49 ` netdev-bot+sashiko
2026-11-05 12:50 ` [PATCH net v5 2/5] amt: reject a gateway Query or Data from 0.0.0.0 before a relay is learned Omar Ramadan
2026-11-09 14:49 ` netdev-bot+sashiko
2026-11-05 12:50 ` [PATCH net v5 3/5] amt: require an exact IPv4-sized IFLA_AMT_{LOCAL,DISCOVERY}_IP Omar Ramadan
2026-11-05 12:50 ` [PATCH net v5 4/5] amt: make pre-query report drops visible Omar Ramadan
2026-11-09 14:49 ` netdev-bot+sashiko [this message]
2026-11-05 12:50 ` [PATCH net v5 5/5] amt: harden relay authentication and teardown Omar Ramadan
2026-11-06 12:50 ` sashiko-bot
2026-11-09 14:49 ` netdev-bot+sashiko
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=179423575970.994134.5432026388018419992@kernel.org \
--to=netdev-bot+sashiko@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=ap420073@gmail.com \
--cc=bigeasy@linutronix.de \
--cc=clrkwllms@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-devel@lists.linux.dev \
--cc=netdev@vger.kernel.org \
--cc=omar@blockcast.net \
--cc=pabeni@redhat.com \
--cc=rostedt@goodmis.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
all inboxes | Powered by JetHome®