From: Sander Vanheule <sander@svanheule.net>
To: sashiko@lists.linux.dev, Rustam Adilov <adilov@disroot.org>,
Guenter Roeck <linux@roeck-us.net>
Cc: krzk+dt@kernel.org, conor+dt@kernel.org,
devicetree@vger.kernel.org, robh@kernel.org,
linux-watchdog@vger.kernel.org
Subject: Re: [PATCH 3/3] watchdog: realtek-otto: add RTL9607C support
Date: Sun, 17 May 2026 12:39:52 +0200 [thread overview]
Message-ID: <d0b159eefa6bc5abf0d1531acde568396f480500.camel@svanheule.net> (raw)
In-Reply-To: <20260509172748.54B33C2BCB2@smtp.kernel.org>
On Sat, 2026-05-09 at 17:27 +0000, sashiko-bot@kernel.org wrote:
> Also, does the system restart handler sleep in an atomic context?
>
> otto_wdt_restart() {
> [ ... ]
> disable_irq(ctrl->irq_phase1);
> [ ... ]
> }
>
> The otto_wdt_restart() function is a system restart handler executed in an
> atomic context with local interrupts disabled. Since disable_irq() internally
> invokes synchronize_irq(), which uses wait_event() to wait for executing
> interrupt handlers to finish, it can sleep.
>
> Calling a sleeping function with local interrupts disabled triggers a kernel
> panic, and waiting for an IRQ handler to complete while other CPUs are stopped
> during a machine restart can result in a hard deadlock. Should this use
> disable_irq_nosync() instead?
I figured if local interrupts are disabled, then we don't need to disable the
pretimeout interrupt, since it won't get called (and give confusing warnings).
However, doing so results in the output of the pretimeout interrupt handler
being printed when rebooting the system (single-core CPU, both with SMP and
without), so the interrupt is still getting through.
Am I missing something here? Or is this a false positive?
Best,
Sander
next prev parent reply other threads:[~2026-05-17 10:40 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-09 16:30 [PATCH 0/3] watchdog: realtek-otto: Make use of regmap API and add RTL9607C support Rustam Adilov
2026-05-09 16:30 ` [PATCH 1/3] watchdog: realtek-otto: Change to use regmap API Rustam Adilov
2026-05-09 17:16 ` sashiko-bot
2026-05-15 20:48 ` Rustam Adilov
2026-05-15 21:10 ` Sander Vanheule
2026-05-16 18:33 ` Guenter Roeck
2026-05-09 16:31 ` [PATCH 2/3] dt-bindings: watchdog: realtek,otto-wdt: add compatible for RTL9607C Rustam Adilov
2026-05-09 18:13 ` Conor Dooley
2026-05-10 8:19 ` Rustam Adilov
2026-05-11 15:52 ` Conor Dooley
2026-05-13 18:27 ` Rustam Adilov
2026-05-10 19:23 ` Sander Vanheule
2026-05-09 16:31 ` [PATCH 3/3] watchdog: realtek-otto: add RTL9607C support Rustam Adilov
2026-05-09 17:27 ` sashiko-bot
2026-05-10 18:12 ` Sander Vanheule
2026-05-17 10:39 ` Sander Vanheule [this message]
2026-05-10 15:13 ` [PATCH 0/3] watchdog: realtek-otto: Make use of regmap API and " Guenter Roeck
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=d0b159eefa6bc5abf0d1531acde568396f480500.camel@svanheule.net \
--to=sander@svanheule.net \
--cc=adilov@disroot.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=robh@kernel.org \
--cc=sashiko@lists.linux.dev \
/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