From: Przemek Kitszel <przemyslaw.kitszel@intel.com>
To: Aleksandr Loktionov <aleksandr.loktionov@intel.com>
Cc: <netdev@vger.kernel.org>, <intel-wired-lan@lists.osuosl.org>,
<anthony.l.nguyen@intel.com>
Subject: Re: [Intel-wired-lan] [PATCH iwl-net 2/5] iavf: fix error path in iavf_request_misc_irq
Date: Mon, 13 Apr 2026 13:53:27 +0200 [thread overview]
Message-ID: <2a90e151-2e7e-409d-9123-1e261c1a24f9@intel.com> (raw)
In-Reply-To: <20260413073035.4082204-3-aleksandr.loktionov@intel.com>
On 4/13/26 09:30, Aleksandr Loktionov wrote:
> From: Piotr Gardocki <piotrx.gardocki@intel.com>
>
> When request_irq() fails the interrupt vector was not registered for
> the driver. Calling free_irq() on a vector that was never successfully
> requested triggers a kernel warning. Drop the erroneous free_irq()
> call from the error path.
>
> Fixes: 5eae00c57f5e ("i40evf: main driver core")
> Signed-off-by: Piotr Gardocki <piotrx.gardocki@intel.com>
> Signed-off-by: Aleksandr Loktionov <aleksandr.loktionov@intel.com>
> ---
> drivers/net/ethernet/intel/iavf/iavf_main.c | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/drivers/net/ethernet/intel/iavf/iavf_main.c b/drivers/net/ethernet/intel/iavf/iavf_main.c
> index dad001a..ab5f5adc 100644
> --- a/drivers/net/ethernet/intel/iavf/iavf_main.c
> +++ b/drivers/net/ethernet/intel/iavf/iavf_main.c
> @@ -587,7 +587,6 @@ static int iavf_request_misc_irq(struct iavf_adapter *adapter)
> dev_err(&adapter->pdev->dev,
> "request_irq for %s failed: %d\n",
> adapter->misc_vector_name, err);
> - free_irq(adapter->msix_entries[0].vector, netdev);
> }
> return err;
> }
Reviewed-by: Przemek Kitszel <przemyslaw.kitszel@intel.com>
next time please CC netdev on IWL submissions
WARNING: multiple messages have this Message-ID (diff)
From: Przemek Kitszel <przemyslaw.kitszel@intel.com>
To: Aleksandr Loktionov <aleksandr.loktionov@intel.com>
Cc: <netdev@vger.kernel.org>, <intel-wired-lan@lists.osuosl.org>,
<anthony.l.nguyen@intel.com>
Subject: Re: [PATCH iwl-net 2/5] iavf: fix error path in iavf_request_misc_irq
Date: Mon, 13 Apr 2026 13:53:27 +0200 [thread overview]
Message-ID: <2a90e151-2e7e-409d-9123-1e261c1a24f9@intel.com> (raw)
In-Reply-To: <20260413073035.4082204-3-aleksandr.loktionov@intel.com>
On 4/13/26 09:30, Aleksandr Loktionov wrote:
> From: Piotr Gardocki <piotrx.gardocki@intel.com>
>
> When request_irq() fails the interrupt vector was not registered for
> the driver. Calling free_irq() on a vector that was never successfully
> requested triggers a kernel warning. Drop the erroneous free_irq()
> call from the error path.
>
> Fixes: 5eae00c57f5e ("i40evf: main driver core")
> Signed-off-by: Piotr Gardocki <piotrx.gardocki@intel.com>
> Signed-off-by: Aleksandr Loktionov <aleksandr.loktionov@intel.com>
> ---
> drivers/net/ethernet/intel/iavf/iavf_main.c | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/drivers/net/ethernet/intel/iavf/iavf_main.c b/drivers/net/ethernet/intel/iavf/iavf_main.c
> index dad001a..ab5f5adc 100644
> --- a/drivers/net/ethernet/intel/iavf/iavf_main.c
> +++ b/drivers/net/ethernet/intel/iavf/iavf_main.c
> @@ -587,7 +587,6 @@ static int iavf_request_misc_irq(struct iavf_adapter *adapter)
> dev_err(&adapter->pdev->dev,
> "request_irq for %s failed: %d\n",
> adapter->misc_vector_name, err);
> - free_irq(adapter->msix_entries[0].vector, netdev);
> }
> return err;
> }
Reviewed-by: Przemek Kitszel <przemyslaw.kitszel@intel.com>
next time please CC netdev on IWL submissions
next prev parent reply other threads:[~2026-04-13 11:48 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-13 7:30 [Intel-wired-lan] [PATCH iwl-net 0/5] iavf: five correctness fixes Aleksandr Loktionov
2026-04-13 7:30 ` Aleksandr Loktionov
2026-04-13 7:30 ` [Intel-wired-lan] [PATCH iwl-net 1/5] iavf: fix null pointer dereference in iavf_detect_recover_hung Aleksandr Loktionov
2026-04-13 7:30 ` Aleksandr Loktionov
2026-04-15 12:48 ` [Intel-wired-lan] " Simon Horman
2026-04-15 12:48 ` Simon Horman
2026-05-11 8:25 ` [Intel-wired-lan] " Romanowski, Rafal
2026-05-11 8:25 ` Romanowski, Rafal
2026-05-11 11:39 ` Loktionov, Aleksandr
2026-05-11 11:39 ` [Intel-wired-lan] " Loktionov, Aleksandr
2026-04-13 7:30 ` [Intel-wired-lan] [PATCH iwl-net 2/5] iavf: fix error path in iavf_request_misc_irq Aleksandr Loktionov
2026-04-13 7:30 ` Aleksandr Loktionov
2026-04-13 11:53 ` Przemek Kitszel [this message]
2026-04-13 11:53 ` Przemek Kitszel
2026-05-11 8:25 ` [Intel-wired-lan] " Romanowski, Rafal
2026-05-11 8:25 ` Romanowski, Rafal
2026-04-15 13:26 ` Simon Horman
2026-04-15 13:26 ` Simon Horman
2026-04-13 7:30 ` [Intel-wired-lan] [PATCH iwl-net 3/5] iavf: prevent VSI corruption when ring params changed during reset Aleksandr Loktionov
2026-04-13 7:30 ` Aleksandr Loktionov
2026-04-15 13:28 ` [Intel-wired-lan] " Simon Horman
2026-04-15 13:28 ` Simon Horman
2026-05-11 8:22 ` [Intel-wired-lan] " Romanowski, Rafal
2026-05-11 8:22 ` Romanowski, Rafal
2026-04-13 7:30 ` [Intel-wired-lan] [PATCH iwl-net 4/5] iavf: fix TC boundary check in iavf_handle_tclass Aleksandr Loktionov
2026-04-13 7:30 ` Aleksandr Loktionov
2026-04-15 13:46 ` [Intel-wired-lan] " Simon Horman
2026-04-15 13:46 ` Simon Horman
2026-05-11 8:22 ` [Intel-wired-lan] " Romanowski, Rafal
2026-05-11 8:22 ` Romanowski, Rafal
2026-05-11 11:32 ` Loktionov, Aleksandr
2026-05-11 11:32 ` [Intel-wired-lan] " Loktionov, Aleksandr
2026-04-13 7:30 ` [Intel-wired-lan] [PATCH iwl-net 5/5] iavf: return 0 when TC flower filter not found after qdisc teardown Aleksandr Loktionov
2026-04-13 7:30 ` Aleksandr Loktionov
2026-04-15 13:53 ` [Intel-wired-lan] " Simon Horman
2026-04-15 13:53 ` Simon Horman
2026-05-11 8:23 ` [Intel-wired-lan] " Romanowski, Rafal
2026-05-11 8:23 ` Romanowski, Rafal
2026-05-11 8:21 ` [Intel-wired-lan] [PATCH iwl-net 0/5] iavf: five correctness fixes Romanowski, Rafal
2026-05-11 8:21 ` Romanowski, Rafal
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=2a90e151-2e7e-409d-9123-1e261c1a24f9@intel.com \
--to=przemyslaw.kitszel@intel.com \
--cc=aleksandr.loktionov@intel.com \
--cc=anthony.l.nguyen@intel.com \
--cc=intel-wired-lan@lists.osuosl.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.