Netdev List
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Ido Schimmel <idosch@nvidia.com>
Cc: zhilinz@nebusec.ai, netdev@vger.kernel.org, dsahern@kernel.org,
	davem@davemloft.net, edumazet@google.com, pabeni@redhat.com,
	horms@kernel.org, leone4fernando@gmail.com, vega@nebusec.ai
Subject: Re: [PATCH net v3 1/1] ipmr: only copy pktinfo to cache reports
Date: Wed, 5 Aug 2026 16:36:24 -0700	[thread overview]
Message-ID: <20260805163624.312b4df7@kernel.org> (raw)
In-Reply-To: <20260805081737.GA1284302@shredder>

On Wed, 5 Aug 2026 11:17:37 +0300 Ido Schimmel wrote:
> On Tue, Aug 04, 2026 at 06:31:26PM -0700, Jakub Kicinski wrote:
> > This is an AI-generated review of your patch. The human sending this
> > email says "Looks legit, let's fix both in one patch?"  
> 
> I suggested [1], but the bug in the IGMPMSG_WHOLEPKT /
> IGMPMSG_WRVIFWHOLE branch needs a different Fixes tag (it precedes
> bb7403655b3c) and Sashiko [2][3] found another bug in this code:
> 
> ipv4_pktinfo_prepare() modifies the control block of 'pkt', which can
> result in this packet being processed incorrectly after
> ipmr_cache_report() returns. I *think* that [4] takes care of it, but
> all of this needs to be explained in the commit message which should
> carry the appropriate Fixes tags (bb7403655b3c + 1da177e4c3f4).

TBH no strong preference on the geometry of the patches (could also 
be two fixes in a series I guess?)  It'd be great if we could start
grouping the sufficiently similar fixes a little bit more. Otherwise
it's increasingly hard to make sense of the patch queue for me, if
nothing else.

> Note that this upcall is not fast path, so the extra work shouldn't be a
> problem.
> 
> Is this what you prefer?

diff looks good at a glance..

  reply	other threads:[~2026-08-05 23:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-03  1:17 [PATCH net v3 1/1] ipmr: only copy pktinfo to cache reports Zhiling Zou
2026-08-04  7:26 ` Ido Schimmel
2026-08-05  1:31 ` Jakub Kicinski
2026-08-05  8:17   ` Ido Schimmel
2026-08-05 23:36     ` Jakub Kicinski [this message]
2026-08-06 10:38       ` Ido Schimmel
2026-08-05 23:37     ` Jakub Kicinski
2026-08-06 10:55       ` Ido Schimmel

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=20260805163624.312b4df7@kernel.org \
    --to=kuba@kernel.org \
    --cc=davem@davemloft.net \
    --cc=dsahern@kernel.org \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=idosch@nvidia.com \
    --cc=leone4fernando@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=vega@nebusec.ai \
    --cc=zhilinz@nebusec.ai \
    /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