From: Simon Horman <horms@kernel.org>
To: Martyna Szapar-Mudlaw <martyna.szapar-mudlaw@linux.intel.com>
Cc: intel-wired-lan@lists.osuosl.org, netdev@vger.kernel.org
Subject: Re: [Intel-wired-lan] [iwl-net 0/4] ice: improve validation of virtchnl parameters
Date: Tue, 18 Feb 2025 19:44:15 +0000 [thread overview]
Message-ID: <20250218194415.GL1615191@kernel.org> (raw)
In-Reply-To: <20250217102744.300357-2-martyna.szapar-mudlaw@linux.intel.com>
On Mon, Feb 17, 2025 at 11:27:41AM +0100, Martyna Szapar-Mudlaw wrote:
> This patch series introduces improvements to the `ice` driver and `virtchnl`
> interface by adding stricter validation checks and preventing potential
> out-of-bounds scenarios.
Hi Martyna,
The above talks about this patchset in terms of improvements rather than
bug fixes (that manifest). If so, I think this should be targeted at
iwl-next (i.e. net-next) rather than iwl-net (net). And the Fixes tags
should be dropped.
...
next prev parent reply other threads:[~2025-02-18 19:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-17 10:27 [Intel-wired-lan] [iwl-net 0/4] ice: improve validation of virtchnl parameters Martyna Szapar-Mudlaw
2025-02-17 10:27 ` [Intel-wired-lan] [iwl-net 1/4] virtchnl: make proto and filter action count unsigned Martyna Szapar-Mudlaw
2025-02-17 10:27 ` [Intel-wired-lan] [iwl-net 2/4] ice: stop truncating queue ids when checking Martyna Szapar-Mudlaw
2025-02-17 10:27 ` [Intel-wired-lan] [iwl-net 3/4] ice: validate queue quanta parameters to prevent OOB access Martyna Szapar-Mudlaw
2025-02-17 10:27 ` [Intel-wired-lan] [iwl-net 4/4] ice: fix input validation for virtchnl BW Martyna Szapar-Mudlaw
2025-02-18 19:44 ` Simon Horman [this message]
2025-02-25 9:24 ` [Intel-wired-lan] [iwl-net 0/4] ice: improve validation of virtchnl parameters Szapar-Mudlaw, Martyna
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=20250218194415.GL1615191@kernel.org \
--to=horms@kernel.org \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=martyna.szapar-mudlaw@linux.intel.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