From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Duoming Zhou <duoming@zju.edu.cn>
Cc: linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
linus.walleij@linaro.org
Subject: Re: [PATCH] Input: cyttsp4_core - change del_timer_sync() to timer_shutdown_sync()
Date: Mon, 1 May 2023 17:38:50 -0700 [thread overview]
Message-ID: <ZFBbmml9FjXICHUv@google.com> (raw)
In-Reply-To: <20230421082919.8471-1-duoming@zju.edu.cn>
On Fri, Apr 21, 2023 at 04:29:19PM +0800, Duoming Zhou wrote:
> The watchdog_timer can schedule tx_timeout_task and watchdog_work
> can also arm watchdog_timer. The process is shown below:
>
> ----------- timer schedules work ------------
> cyttsp4_watchdog_timer() //timer handler
> schedule_work(&cd->watchdog_work)
>
> ----------- work arms timer ------------
> cyttsp4_watchdog_work() //workqueue callback function
> cyttsp4_start_wd_timer()
> mod_timer(&cd->watchdog_timer, ...)
>
> Although del_timer_sync() and cancel_work_sync() are called in
> cyttsp4_remove(), the timer and workqueue could still be rearmed.
> As a result, the possible use after free bugs could happen. The
> process is shown below:
>
> (cleanup routine) | (timer and workqueue routine)
> cyttsp4_remove() | cyttsp4_watchdog_timer() //timer
> cyttsp4_stop_wd_timer() | schedule_work()
> del_timer_sync() |
> | cyttsp4_watchdog_work() //worker
> | cyttsp4_start_wd_timer()
> | mod_timer()
> cancel_work_sync() |
> | cyttsp4_watchdog_timer() //timer
> | schedule_work()
> del_timer_sync() |
> kfree(cd) //FREE |
> | cyttsp4_watchdog_work() // reschedule!
> | cd-> //USE
>
> This patch changes del_timer_sync() to timer_shutdown_sync(),
> which could prevent rearming of the timer from the workqueue.
>
> Fixes: 17fb1563d69b ("Input: cyttsp4 - add core driver for Cypress TMA4XX touchscreen devices")
> Signed-off-by: Duoming Zhou <duoming@zju.edu.cn>
Applied, thank you.
--
Dmitry
prev parent reply other threads:[~2023-05-02 0:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-21 8:29 Duoming Zhou
2023-05-02 0:38 ` Dmitry Torokhov [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=ZFBbmml9FjXICHUv@google.com \
--to=dmitry.torokhov@gmail.com \
--cc=duoming@zju.edu.cn \
--cc=linus.walleij@linaro.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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®