From: Brett Creeley <bcreeley@amd.com>
To: Marcin Szycik <marcin.szycik@linux.intel.com>,
intel-wired-lan@lists.osuosl.org
Cc: netdev@vger.kernel.org, mateusz.polchlopek@intel.com,
maciej.fijalkowski@intel.com,
Przemek Kitszel <przemyslaw.kitszel@intel.com>
Subject: Re: [PATCH iwl-net v3 2/2] ice: Fix netif_is_ice() in Safe Mode
Date: Tue, 24 Sep 2024 11:48:25 -0700 [thread overview]
Message-ID: <f2b5ece9-0167-46f4-94fc-28b48c489e0e@amd.com> (raw)
In-Reply-To: <20240924100422.8010-4-marcin.szycik@linux.intel.com>
On 9/24/2024 3:04 AM, Marcin Szycik wrote:
> Caution: This message originated from an External Source. Use proper caution when opening attachments, clicking links, or responding.
>
>
> netif_is_ice() works by checking the pointer to netdev ops. However, it
> only checks for the default ice_netdev_ops, not ice_netdev_safe_mode_ops,
> so in Safe Mode it always returns false, which is unintuitive. While it
> doesn't look like netif_is_ice() is currently being called anywhere in Safe
> Mode, this could change and potentially lead to unexpected behaviour.
>
> Fixes: df006dd4b1dc ("ice: Add initial support framework for LAG")
> Reviewed-by: Przemek Kitszel <przemyslaw.kitszel@intel.com>
> Signed-off-by: Marcin Szycik <marcin.szycik@linux.intel.com>
> ---
> drivers/net/ethernet/intel/ice/ice_main.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/net/ethernet/intel/ice/ice_main.c b/drivers/net/ethernet/intel/ice/ice_main.c
> index 7a84d3c4c305..b1e7727b8677 100644
> --- a/drivers/net/ethernet/intel/ice/ice_main.c
> +++ b/drivers/net/ethernet/intel/ice/ice_main.c
> @@ -87,7 +87,8 @@ ice_indr_setup_tc_cb(struct net_device *netdev, struct Qdisc *sch,
>
> bool netif_is_ice(const struct net_device *dev)
> {
> - return dev && (dev->netdev_ops == &ice_netdev_ops);
> + return dev && (dev->netdev_ops == &ice_netdev_ops ||
> + dev->netdev_ops == &ice_netdev_safe_mode_ops);
> }
LGTM.
Reviewed-by: Brett Creeley <brett.creeley@amd.com>
>
> /**
> --
> 2.45.0
>
next prev parent reply other threads:[~2024-09-24 18:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-24 10:04 [PATCH iwl-net v3 1/2] ice: Fix entering Safe Mode Marcin Szycik
2024-09-24 10:04 ` [PATCH iwl-net v3 2/2] ice: Fix netif_is_ice() in " Marcin Szycik
2024-09-24 18:48 ` Brett Creeley [this message]
2024-10-04 10:37 ` [Intel-wired-lan] " Buvaneswaran, Sujai
2024-09-24 18:49 ` [PATCH iwl-net v3 1/2] ice: Fix entering " Brett Creeley
2024-09-28 16:31 ` [Intel-wired-lan] " Pucha, HimasekharX Reddy
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=f2b5ece9-0167-46f4-94fc-28b48c489e0e@amd.com \
--to=bcreeley@amd.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=maciej.fijalkowski@intel.com \
--cc=marcin.szycik@linux.intel.com \
--cc=mateusz.polchlopek@intel.com \
--cc=netdev@vger.kernel.org \
--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).