From: Guenter Roeck <linux@roeck-us.net>
To: Chengfeng Ye <dg573847474@gmail.com>,
krzysztof.kozlowski@linaro.org, alim.akhtar@samsung.com,
wim@linux-watchdog.org
Cc: linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org,
linux-watchdog@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] watchdog: s3c2410: Fix potential deadlock on &wdt->lock
Date: Wed, 5 Jul 2023 07:53:11 -0700 [thread overview]
Message-ID: <7266dc04-8db3-a48b-6844-8530ae7b8adf@roeck-us.net> (raw)
In-Reply-To: <20230705090951.63762-1-dg573847474@gmail.com>
On 7/5/23 02:09, Chengfeng Ye wrote:
> As &wdt->lock is acquired by hard irq s3c2410wdt_irq(),
> other acquisition of the same lock under process context should
> disable irq, otherwise deadlock could happen if the
> irq preempt the execution while the lock is held in process context
> on the same CPU.
>
> [Deadlock Scenario]
> s3c2410wdt_suspend()
> -> s3c2410wdt_stop()
> -> spin_lock(&wdt->lock)
> <irq iterrupt>
> -> s3c2410wdt_irq()
> -> s3c2410wdt_keepalive()
> -> spin_lock(&wdt->lock) (deadlock here)
>
> [Deadlock Scenario]
> s3c2410wdt_probe()
> -> s3c2410wdt_start()
> -> spin_lock(&wdt->lock)
> <irq iterrupt>
> -> s3c2410wdt_irq()
> -> s3c2410wdt_keepalive()
> -> spin_lock(&wdt->lock) (deadlock here)
>
> [Deadlock Scenario]
> s3c2410wdt_keepalive()
> -> spin_lock(&wdt->lock)
> <irq iterrupt>
> -> s3c2410wdt_irq()
> -> s3c2410wdt_keepalive()
> -> spin_lock(&wdt->lock) (deadlock here)
>
> This flaw was found by an experimental static analysis tool I am
> developing for irq-related deadlock, which reported the above
> warning when analyzing the linux kernel 6.4-rc7 release.
>
> The tentative patch fix the potential deadlock by spin_lock_irqsave()
> under process context.
>
> Signed-off-by: Chengfeng Ye <dg573847474@gmail.com>
Reviewed-by: Guenter Roeck <linux@roeck-us.net>
> ---
> drivers/watchdog/s3c2410_wdt.c | 15 +++++++++------
> 1 file changed, 9 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/watchdog/s3c2410_wdt.c b/drivers/watchdog/s3c2410_wdt.c
> index 95416a9bdd4b..e1dc71ece01e 100644
> --- a/drivers/watchdog/s3c2410_wdt.c
> +++ b/drivers/watchdog/s3c2410_wdt.c
> @@ -379,10 +379,11 @@ static int s3c2410wdt_enable(struct s3c2410_wdt *wdt, bool en)
> static int s3c2410wdt_keepalive(struct watchdog_device *wdd)
> {
> struct s3c2410_wdt *wdt = watchdog_get_drvdata(wdd);
> + unsigned long flags;
>
> - spin_lock(&wdt->lock);
> + spin_lock_irqsave(&wdt->lock, flags);
> writel(wdt->count, wdt->reg_base + S3C2410_WTCNT);
> - spin_unlock(&wdt->lock);
> + spin_unlock_irqrestore(&wdt->lock, flags);
>
> return 0;
> }
> @@ -399,10 +400,11 @@ static void __s3c2410wdt_stop(struct s3c2410_wdt *wdt)
> static int s3c2410wdt_stop(struct watchdog_device *wdd)
> {
> struct s3c2410_wdt *wdt = watchdog_get_drvdata(wdd);
> + unsigned long flags;
>
> - spin_lock(&wdt->lock);
> + spin_lock_irqsave(&wdt->lock, flags);
> __s3c2410wdt_stop(wdt);
> - spin_unlock(&wdt->lock);
> + spin_unlock_irqrestore(&wdt->lock, flags);
>
> return 0;
> }
> @@ -411,8 +413,9 @@ static int s3c2410wdt_start(struct watchdog_device *wdd)
> {
> unsigned long wtcon;
> struct s3c2410_wdt *wdt = watchdog_get_drvdata(wdd);
> + unsigned long flags;
>
> - spin_lock(&wdt->lock);
> + spin_lock_irqsave(&wdt->lock, flags);
>
> __s3c2410wdt_stop(wdt);
>
> @@ -433,7 +436,7 @@ static int s3c2410wdt_start(struct watchdog_device *wdd)
> writel(wdt->count, wdt->reg_base + S3C2410_WTDAT);
> writel(wdt->count, wdt->reg_base + S3C2410_WTCNT);
> writel(wtcon, wdt->reg_base + S3C2410_WTCON);
> - spin_unlock(&wdt->lock);
> + spin_unlock_irqrestore(&wdt->lock, flags);
>
> return 0;
> }
next prev parent reply other threads:[~2023-07-05 14:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-05 9:09 Chengfeng Ye
2023-07-05 9:37 ` Krzysztof Kozlowski
2023-07-05 12:51 ` Guenter Roeck
2023-07-05 14:40 ` Chengfeng Ye
2023-07-05 14:53 ` Guenter Roeck [this message]
2023-07-19 18:39 ` Chengfeng Ye
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=7266dc04-8db3-a48b-6844-8530ae7b8adf@roeck-us.net \
--to=linux@roeck-us.net \
--cc=alim.akhtar@samsung.com \
--cc=dg573847474@gmail.com \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=wim@linux-watchdog.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 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®