From: gregory.herrero@oracle.com
To: aleksandr.loktionov@intel.com, anthony.l.nguyen@intel.com,
przemyslaw.kitszel@intel.com, andrew+netdev@lunn.ch,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com
Cc: intel-wired-lan@lists.osuosl.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org,
Gregory Herrero <gregory.herrero@oracle.com>
Subject: [PATCH v4 0/1] i40e: additional safety check
Date: Mon, 17 Nov 2025 09:33:25 +0100 [thread overview]
Message-ID: <20251117083326.2784380-1-gregory.herrero@oracle.com> (raw)
From: Gregory Herrero <gregory.herrero@oracle.com>
On code inspection, I realized we may want to check ring_len parameter
against hardware specific values in i40e_config_vsi_tx_queue() and
i40e_config_vsi_rx_queue().
v4:
- remove u32 cast in i40e_config_vsi_tx_queue() too and don't mention it
anymore in commit description.
- wrap i40e_get_max_num_descriptors() description
v3:
- drop trailing period from the subject
- reword commit description
- remove u32 cast in i40e_config_vsi_rx_queue()
v2:
- make i40e_get_max_num_descriptors() 'pf' argument const.
- reword i40e_get_max_num_descriptors() description.
- modify commit description to explain potential behavior change.
Gregory Herrero (1):
i40e: validate ring_len parameter against hardware-specific values
drivers/net/ethernet/intel/i40e/i40e.h | 18 ++++++++++++++++++
drivers/net/ethernet/intel/i40e/i40e_ethtool.c | 12 ------------
.../net/ethernet/intel/i40e/i40e_virtchnl_pf.c | 4 ++--
3 files changed, 20 insertions(+), 14 deletions(-)
--
2.51.0
next reply other threads:[~2025-11-17 8:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-17 8:33 gregory.herrero [this message]
2025-11-17 8:33 ` [PATCH v4 1/1] i40e: validate ring_len parameter against hardware-specific values gregory.herrero
2025-11-17 11:58 ` Loktionov, Aleksandr
2025-12-11 8:38 ` Romanowski, Rafal
2025-12-12 20:20 ` Gregory Herrero
2025-12-12 17:37 ` Creeley, Brett
2025-12-12 20:22 ` Gregory Herrero
2025-12-12 20:45 ` Creeley, Brett
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=20251117083326.2784380-1-gregory.herrero@oracle.com \
--to=gregory.herrero@oracle.com \
--cc=aleksandr.loktionov@intel.com \
--cc=andrew+netdev@lunn.ch \
--cc=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=przemyslaw.kitszel@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox