From: Phil Chang <phil.chang@mediatek.com>
To: <phil.chang@mediatek.com>
Cc: <anna-maria@linutronix.de>, <frederic@kernel.org>,
<tglx@linutronix.de>, <matthias.bgg@gmail.com>,
<angelogioacchino.delregno@collabora.com>,
<linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>, <jy.ho@mediatek.com>,
<alix.wu@mediatk.com>
Subject: [PATCH] hrtimer: check hrtimer with a NULL function
Date: Wed, 5 Jun 2024 16:41:49 +0800 [thread overview]
Message-ID: <20240605084149.6420-1-phil.chang@mediatek.com> (raw)
simillar with timers, check for timer->function == NULL.
If the pointer is NULL, discard the request silently.
Signed-off-by: Phil Chang <phil.chang@mediatek.com>
---
kernel/time/hrtimer.c | 10 ++++++++++
1 file changed, 10 insertions(+)
diff --git a/kernel/time/hrtimer.c b/kernel/time/hrtimer.c
index 492c14aac642..72d6e7bc9cd9 100644
--- a/kernel/time/hrtimer.c
+++ b/kernel/time/hrtimer.c
@@ -1297,9 +1297,13 @@ void hrtimer_start_range_ns(struct hrtimer *timer, ktime_t tim,
base = lock_hrtimer_base(timer, &flags);
+ if (!timer->function)
+ goto out;
+
if (__hrtimer_start_range_ns(timer, tim, delta_ns, mode, base))
hrtimer_reprogram(timer, true);
+out:
unlock_hrtimer_base(timer, &flags);
}
EXPORT_SYMBOL_GPL(hrtimer_start_range_ns);
@@ -1667,6 +1671,11 @@ static void __run_hrtimer(struct hrtimer_cpu_base *cpu_base,
__remove_hrtimer(timer, base, HRTIMER_STATE_INACTIVE, 0);
fn = timer->function;
+ if (WARN_ON_ONCE(!fn)) {
+ /* Should never happen. */
+ goto out;
+ }
+
/*
* Clear the 'is relative' flag for the TIME_LOW_RES case. If the
* timer is restarted with a period then it becomes an absolute
@@ -1710,6 +1719,7 @@ static void __run_hrtimer(struct hrtimer_cpu_base *cpu_base,
* hrtimer_active() cannot observe base->running.timer == NULL &&
* timer->state == INACTIVE.
*/
+out:
raw_write_seqcount_barrier(&base->seq);
WARN_ON_ONCE(base->running != timer);
--
2.18.0
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2024-06-05 8:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-05 8:41 Phil Chang [this message]
2024-06-05 10:15 ` [PATCH] hrtimer: check hrtimer with a NULL function Anna-Maria Behnsen
2024-06-05 13:51 ` Phil Chang
2024-06-06 13:14 ` Anna-Maria Behnsen
2024-06-07 2:26 ` [PATCH v2] " Phil Chang
2024-06-10 9:47 ` Anna-Maria Behnsen
2024-06-10 13:31 ` [PATCH v3] " Phil Chang
2024-06-17 16:19 ` Anna-Maria Behnsen
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=20240605084149.6420-1-phil.chang@mediatek.com \
--to=phil.chang@mediatek.com \
--cc=alix.wu@mediatk.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=anna-maria@linutronix.de \
--cc=frederic@kernel.org \
--cc=jy.ho@mediatek.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=tglx@linutronix.de \
/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;
as well as URLs for NNTP newsgroup(s).