From: Jacob Keller <jacob.e.keller@intel.com>
To: Rosen Penev <rosenp@gmail.com>, <netdev@vger.kernel.org>
Cc: <davem@davemloft.net>, <edumazet@google.com>, <kuba@kernel.org>,
<pabeni@redhat.com>, <linux@armlinux.org.uk>,
<linux-kernel@vger.kernel.org>, <o.rempel@pengutronix.de>,
<p.zabel@pengutronix.de>
Subject: Re: [PATCH net-next] net: ag71xx: disable napi interrupts during probe
Date: Wed, 28 Aug 2024 14:05:46 -0700 [thread overview]
Message-ID: <cabb111b-37b4-493c-ad6c-c237c7091bf6@intel.com> (raw)
In-Reply-To: <20240828204135.6543-1-rosenp@gmail.com>
On 8/28/2024 1:41 PM, Rosen Penev wrote:
> From: Sven Eckelmann <sven@narfation.org>
>
> ag71xx_probe is registering ag71xx_interrupt as handler for gmac0/gmac1
> interrupts. The handler is trying to use napi_schedule to handle the
> processing of packets. But the netif_napi_add for this device is
> called a lot later in ag71xx_probe.
>
> It can therefore happen that a still running gmac0/gmac1 is triggering the
> interrupt handler with a bit from AG71XX_INT_POLL set in
> AG71XX_REG_INT_STATUS. The handler will then call napi_schedule and the
> napi code will crash the system because the ag->napi is not yet
> initialized.
>
> The gmcc0/gmac1 must be brought in a state in which it doesn't signal a
> AG71XX_INT_POLL related status bits as interrupt before registering the
> interrupt handler. ag71xx_hw_start will take care of re-initializing the
> AG71XX_REG_INT_ENABLE.
>
> Signed-off-by: Sven Eckelmann <sven@narfation.org>
> Signed-off-by: Rosen Penev <rosenp@gmail.com>
> ---
The description reads like a bug fix, so I would expect this to be
targeted to net and have a Fixes tag indicating what commit introduced
the issue, maybe:
Fixes: d51b6ce441d3 ("net: ethernet: add ag71xx driver")
The change seems reasonable to me otherwise.
> drivers/net/ethernet/atheros/ag71xx.c | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/drivers/net/ethernet/atheros/ag71xx.c b/drivers/net/ethernet/atheros/ag71xx.c
> index 0674a042e8d3..435c4b19acdd 100644
> --- a/drivers/net/ethernet/atheros/ag71xx.c
> +++ b/drivers/net/ethernet/atheros/ag71xx.c
> @@ -1855,6 +1855,12 @@ static int ag71xx_probe(struct platform_device *pdev)
> if (!ag->mac_base)
> return -ENOMEM;
>
> + /* ensure that HW is in manual polling mode before interrupts are
> + * activated. Otherwise ag71xx_interrupt might call napi_schedule
> + * before it is initialized by netif_napi_add.
> + */
> + ag71xx_int_disable(ag, AG71XX_INT_POLL);
> +
> ndev->irq = platform_get_irq(pdev, 0);
> err = devm_request_irq(&pdev->dev, ndev->irq, ag71xx_interrupt,
> 0x0, dev_name(&pdev->dev), ndev);
next prev parent reply other threads:[~2024-08-28 21:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-28 20:41 [PATCH net-next] net: ag71xx: disable napi interrupts during probe Rosen Penev
2024-08-28 21:05 ` Jacob Keller [this message]
2024-08-29 17:46 ` Rosen Penev
2024-08-29 17:50 ` Keller, Jacob E
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=cabb111b-37b4-493c-ad6c-c237c7091bf6@intel.com \
--to=jacob.e.keller@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=o.rempel@pengutronix.de \
--cc=p.zabel@pengutronix.de \
--cc=pabeni@redhat.com \
--cc=rosenp@gmail.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