From: Ido Schimmel <idosch@nvidia.com>
To: Zhiling Zou <zhilinz@nebusec.ai>
Cc: netdev@vger.kernel.org, dsahern@kernel.org, davem@davemloft.net,
edumazet@kernel.org, pabeni@redhat.com, horms@kernel.org,
vega@nebusec.ai
Subject: Re: [PATCH net 0/1] ipmr: validate VIF indexes before offload lookup
Date: Thu, 15 Oct 2026 14:52:48 +0300 [thread overview]
Message-ID: <20261015115248.GB1716181@shredder> (raw)
In-Reply-To: <cover.1791899747.git.zhilinz@nebusec.ai>
On Tue, Oct 13, 2026 at 10:33:56PM +0800, Zhiling Zou wrote:
> Hi Linux kernel maintainers,
>
> We found and validated an issue in net/ipv4/ipmr.c.
It's quite frustrating to see this given that you abandoned a previous
ipmr bug fix:
https://lore.kernel.org/netdev/20260903113055.GA90787@shredder/
prev parent reply other threads:[~2026-10-15 11:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-13 14:33 [PATCH net 0/1] ipmr: validate VIF indexes before offload lookup Zhiling Zou
2026-10-13 14:33 ` [PATCH net 1/1] " Zhiling Zou
2026-10-15 11:45 ` Ido Schimmel
2026-10-13 14:40 ` [PATCH net 0/1] " netdev-bot+sinfo
2026-10-15 11:52 ` Ido Schimmel [this message]
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=20261015115248.GB1716181@shredder \
--to=idosch@nvidia.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@kernel.org \
--cc=horms@kernel.org \
--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