intel-wired-lan.osuosl.org archive mirror
 help / color / mirror / Atom feed
From: Cody Haas <chaas@riotgames.com>
To: intel-wired-lan@lists.osuosl.org
Cc: 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
Subject: [Intel-wired-lan] [BUG] ethtool_get_rxfh_indir will always fail with EINVAL for ice driver devices
Date: Thu, 30 Oct 2025 11:40:24 -0700	[thread overview]
Message-ID: <CAH7f-UKkJV8MLY7zCdgCrGE55whRhbGAXvgkDnwgiZ9gUZT7_w@mail.gmail.com> (raw)

Hey there!

I believe I may have encountered a bug with the ice driver. I'm currently
evaluating a few e810 NICs using the ice in-tree driver for kernel
6.16.5-200.fc42.x86_64, and noticed I am unable to get the indirection table
using ethtool_get_rxfh_indir via ioctl. Doing some tracing it looks like
ethtool_get_rxfh_indir calls ice_get_rxfh, which then calls ice_get_rss_key.
In this call sequence the seed passed into ice_get_rss_key will always be null
as ethtool_get_rxfh_indir does not set the key in struct ethtool_rxfh_param
*rxfh and ice_get_rxfh passes the value through to ice_get_rss_key as
*seed without checking if it is null. Then ice_get_rss_key(..) will return
EINVAL when *seed is null.

I compared this to the behavior of the i40e driver, which is the driver we
currently use on our devices. It looks like this can happen on the i40e driver,
however since i40e_get_rxfh has the lookup table (lut) that it creates
locally it will be able to retrieve the indirection table via
ethtool_get_rxfh_indir.

Is this behavior in the ice driver intended? If no, I've got an idea on how to
go about fixing this. Do you have any documentation for creating a patch
for the ice driver? Also I've never done a kernel bisect before, and the
machine that's running the ice driver is quite slow at compiling the kernel.
If anyone knows when this might have been introduced that would be very
helpful.

We're currently evaluating these cards on a timeframe so any help would be
greatly appreciated.

Thanks!

Cody Haas

             reply	other threads:[~2025-10-30 18:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-30 18:40 Cody Haas [this message]
2025-11-12 14:01 ` [Intel-wired-lan] [BUG] ethtool_get_rxfh_indir will always fail with EINVAL for ice driver devices Przemek Kitszel

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=CAH7f-UKkJV8MLY7zCdgCrGE55whRhbGAXvgkDnwgiZ9gUZT7_w@mail.gmail.com \
    --to=chaas@riotgames.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=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;
as well as URLs for NNTP newsgroup(s).