From: Vladimir Oltean <vladimir.oltean@nxp.com>
To: Pavel Skripkin <paskripkin@gmail.com>
Cc: Claudiu Manoil <claudiu.manoil@nxp.com>,
"alexandre.belloni@bootlin.com" <alexandre.belloni@bootlin.com>,
"davem@davemloft.net" <davem@davemloft.net>,
"edumazet@google.com" <edumazet@google.com>,
"kuba@kernel.org" <kuba@kernel.org>,
"pabeni@redhat.com" <pabeni@redhat.com>,
"clement.leger@bootlin.com" <clement.leger@bootlin.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Andrew Lunn <andrew@lunn.ch>
Subject: Re: [PATCH v3] net: ocelot: fix wrong time_after usage
Date: Wed, 6 Jul 2022 13:13:01 +0000 [thread overview]
Message-ID: <20220706131300.uontjopbdf72pwxy@skbuf> (raw)
In-Reply-To: <20220706105044.8071-1-paskripkin@gmail.com>
Hi Pavel,
On Wed, Jul 06, 2022 at 01:50:44PM +0300, Pavel Skripkin wrote:
> Accidentally noticed, that this driver is the only user of
> while (time_after(jiffies...)).
>
> It looks like typo, because likely this while loop will finish after 1st
> iteration, because time_after() returns true when 1st argument _is after_
> 2nd one.
>
> There is one possible problem with this poll loop: the scheduler could put
> the thread to sleep, and it does not get woken up for
> OCELOT_FDMA_CH_SAFE_TIMEOUT_US. During that time, the hardware has done
> its thing, but you exit the while loop and return -ETIMEDOUT.
>
> Fix it by using sane poll API that avoids all problems described above
>
> Fixes: 753a026cfec1 ("net: ocelot: add FDMA support")
> Suggested-by: Andrew Lunn <andrew@lunn.ch>
> Signed-off-by: Pavel Skripkin <paskripkin@gmail.com>
> ---
>
> Changes since v2:
> - Use _atomic variant of readx_poll_timeout
>
> Changes since v1:
> - Fixed typos in title and commit message
> - Remove while loop and use readx_poll_timeout as suggested by
> Andrew
>
> ---
> drivers/net/ethernet/mscc/ocelot_fdma.c | 17 ++++++++---------
> 1 file changed, 8 insertions(+), 9 deletions(-)
>
> diff --git a/drivers/net/ethernet/mscc/ocelot_fdma.c b/drivers/net/ethernet/mscc/ocelot_fdma.c
> index 083fddd263ec..c93fba0a2a7d 100644
> --- a/drivers/net/ethernet/mscc/ocelot_fdma.c
> +++ b/drivers/net/ethernet/mscc/ocelot_fdma.c
> @@ -94,19 +94,18 @@ static void ocelot_fdma_activate_chan(struct ocelot *ocelot, dma_addr_t dma,
> ocelot_fdma_writel(ocelot, MSCC_FDMA_CH_ACTIVATE, BIT(chan));
> }
>
> +static u32 ocelot_fdma_read_ch_safe(struct ocelot *ocelot)
> +{
> + return ocelot_fdma_readl(ocelot, MSCC_FDMA_CH_SAFE);
> +}
> +
> static int ocelot_fdma_wait_chan_safe(struct ocelot *ocelot, int chan)
> {
> - unsigned long timeout;
> u32 safe;
>
> - timeout = jiffies + usecs_to_jiffies(OCELOT_FDMA_CH_SAFE_TIMEOUT_US);
> - do {
> - safe = ocelot_fdma_readl(ocelot, MSCC_FDMA_CH_SAFE);
> - if (safe & BIT(chan))
> - return 0;
> - } while (time_after(jiffies, timeout));
> -
> - return -ETIMEDOUT;
> + return readx_poll_timeout_atomic(ocelot_fdma_read_ch_safe, ocelot, safe,
> + safe & BIT(chan), 0,
> + OCELOT_FDMA_CH_SAFE_TIMEOUT_US);
Can you please indent the arguments to the open bracket?
> }
>
> static void ocelot_fdma_dcb_set_data(struct ocelot_fdma_dcb *dcb,
> --
> 2.35.1
>
next prev parent reply other threads:[~2022-07-06 13:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-06 10:50 [PATCH v3] net: ocelot: fix wrong time_after usage Pavel Skripkin
2022-07-06 13:13 ` Vladimir Oltean [this message]
2022-07-06 13:29 ` Pavel Skripkin
2022-07-06 13:30 ` Vladimir Oltean
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=20220706131300.uontjopbdf72pwxy@skbuf \
--to=vladimir.oltean@nxp.com \
--cc=alexandre.belloni@bootlin.com \
--cc=andrew@lunn.ch \
--cc=claudiu.manoil@nxp.com \
--cc=clement.leger@bootlin.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=paskripkin@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