From: Sebastian Alba Vives <sebasjosue84@gmail.com>
To: gregkh@linuxfoundation.org, jirislaby@kernel.org, pjw@kernel.org,
samuel.holland@sifive.com
Cc: linux-serial@vger.kernel.org, linux-riscv@lists.infradead.org,
linux-kernel@vger.kernel.org,
Sebastian Alba <sebasjosue84@estudiantec.cr>
Subject: [PATCH 2/2] serial: sifive: avoid division by zero in the clock notifier
Date: Sat, 17 Oct 2026 01:44:53 -0600 [thread overview]
Message-ID: <20261017074453.62645-3-sebasjosue84@gmail.com> (raw)
In-Reply-To: <20261017074453.62645-1-sebasjosue84@gmail.com>
From: Sebastian Alba <sebasjosue84@estudiantec.cr>
sifive_serial_probe() registers the clock rate-change notifier before
it initialises the two fields that notifier divides by. ssp comes from
devm_kzalloc(), so between clk_notifier_register() and the assignments
a few lines below, both ssp->baud_rate and ssp->port.uartclk are zero.
A rate change taken in that window reaches:
PRE_RATE_CHANGE: udelay(DIV_ROUND_UP(12 * 1000 * 1000, ssp->baud_rate))
POST_RATE_CHANGE: __ssp_update_div() ->
DIV_ROUND_UP(ssp->port.uartclk, ssp->baud_rate) - 1
On RISC-V an integer division by zero does not trap; the ISA defines the
result as all bits set. DIV_ROUND_UP() therefore yields ULONG_MAX and
udelay() busy-waits essentially forever, hanging the CPU, rather than
producing a clean oops. The POST_RATE_CHANGE path additionally programs
a bogus divisor into the hardware.
On the FU740 the UART clock is derived from the CPU clock through a
synchronous divide-by-two, as the notifier's own comment describes, so
any CPU rate change during probe can hit this.
Initialise uartclk and baud_rate before registering the notifier, and
bail out early if the notifier is ever called with no baud rate set.
Fixes: 45c054d0815b ("tty: serial: add driver for the SiFive UART")
Signed-off-by: Sebastian Alba <sebasjosue84@estudiantec.cr>
---
drivers/tty/serial/sifive.c | 13 ++++++++-----
1 file changed, 8 insertions(+), 5 deletions(-)
diff --git a/drivers/tty/serial/sifive.c b/drivers/tty/serial/sifive.c
index 4a445d285..cd2925b6a 100644
--- a/drivers/tty/serial/sifive.c
+++ b/drivers/tty/serial/sifive.c
@@ -604,6 +604,9 @@ static int sifive_serial_clk_notifier(struct notifier_block *nb,
struct clk_notifier_data *cnd = data;
struct sifive_serial_port *ssp = notifier_to_sifive_serial_port(nb);
+ if (!ssp->baud_rate)
+ return NOTIFY_OK;
+
if (event == PRE_RATE_CHANGE) {
/*
* The TX watermark is always set to 1 by this driver, which
@@ -1022,6 +1025,11 @@ static int sifive_serial_probe(struct platform_device *pdev)
ssp->clk = clk;
ssp->clk_notifier.notifier_call = sifive_serial_clk_notifier;
+ /* Set up clock divider before the notifier can observe this port */
+ ssp->port.uartclk = clk_get_rate(ssp->clk);
+ ssp->baud_rate = SIFIVE_DEFAULT_BAUD_RATE;
+ __ssp_update_div(ssp);
+
r = clk_notifier_register(ssp->clk, &ssp->clk_notifier);
if (r) {
dev_err(&pdev->dev, "could not register clock notifier: %d\n",
@@ -1029,11 +1037,6 @@ static int sifive_serial_probe(struct platform_device *pdev)
goto probe_out1;
}
- /* Set up clock divider */
- ssp->port.uartclk = clk_get_rate(ssp->clk);
- ssp->baud_rate = SIFIVE_DEFAULT_BAUD_RATE;
- __ssp_update_div(ssp);
-
platform_set_drvdata(pdev, ssp);
/* Enable transmits and set the watermark level to 1 */
--
2.43.0
prev parent reply other threads:[~2026-10-17 7:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-17 7:44 [PATCH 0/2] serial: sifive: fix two init ordering bugs in probe Sebastian Alba Vives
2026-10-17 7:44 ` [PATCH 1/2] serial: sifive: fix NULL pointer dereference in probe IRQ window Sebastian Alba Vives
2026-10-17 7:44 ` Sebastian Alba Vives [this message]
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=20261017074453.62645-3-sebasjosue84@gmail.com \
--to=sebasjosue84@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jirislaby@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux-serial@vger.kernel.org \
--cc=pjw@kernel.org \
--cc=samuel.holland@sifive.com \
--cc=sebasjosue84@estudiantec.cr \
/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
all inboxes | Powered by JetHome®