From: "tip-bot2 for Thomas Gleixner" <tip-bot2@linutronix.de>
To: linux-tip-commits@vger.kernel.org
Cc: Thomas Gleixner <tglx@linutronix.de>,
Frederic Weisbecker <frederic@kernel.org>,
x86@kernel.org, linux-kernel@vger.kernel.org
Subject: [tip: timers/core] posix-timers: Remove a few paranoid warnings
Date: Thu, 13 Mar 2025 11:31:32 -0000 [thread overview]
Message-ID: <174186549209.14745.2321427735841251654.tip-bot2@tip-bot2> (raw)
In-Reply-To: <20250308155623.765462334@linutronix.de>
The following commit has been merged into the timers/core branch of tip:
Commit-ID: 4c5cd058beb565ea02ff3db9236f01b2b7d78071
Gitweb: https://git.kernel.org/tip/4c5cd058beb565ea02ff3db9236f01b2b7d78071
Author: Thomas Gleixner <tglx@linutronix.de>
AuthorDate: Sat, 08 Mar 2025 17:48:24 +01:00
Committer: Thomas Gleixner <tglx@linutronix.de>
CommitterDate: Thu, 13 Mar 2025 12:07:16 +01:00
posix-timers: Remove a few paranoid warnings
Warnings about a non-initialized timer or non-existing callbacks are just
useful for implementing new posix clocks, but there a NULL pointer
dereference is expected anyway. :)
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Reviewed-by: Frederic Weisbecker <frederic@kernel.org>
Link: https://lore.kernel.org/all/20250308155623.765462334@linutronix.de
---
kernel/time/posix-timers.c | 37 ++++++++-----------------------------
1 file changed, 8 insertions(+), 29 deletions(-)
diff --git a/kernel/time/posix-timers.c b/kernel/time/posix-timers.c
index e908846..5591b15 100644
--- a/kernel/time/posix-timers.c
+++ b/kernel/time/posix-timers.c
@@ -682,7 +682,6 @@ void common_timer_get(struct k_itimer *timr, struct itimerspec64 *cur_setting)
static int do_timer_gettime(timer_t timer_id, struct itimerspec64 *setting)
{
- const struct k_clock *kc;
struct k_itimer *timr;
unsigned long flags;
int ret = 0;
@@ -692,11 +691,7 @@ static int do_timer_gettime(timer_t timer_id, struct itimerspec64 *setting)
return -EINVAL;
memset(setting, 0, sizeof(*setting));
- kc = timr->kclock;
- if (WARN_ON_ONCE(!kc || !kc->timer_get))
- ret = -EINVAL;
- else
- kc->timer_get(timr, setting);
+ timr->kclock->timer_get(timr, setting);
unlock_timer(timr, flags);
return ret;
@@ -824,7 +819,6 @@ static void common_timer_wait_running(struct k_itimer *timer)
static struct k_itimer *timer_wait_running(struct k_itimer *timer,
unsigned long *flags)
{
- const struct k_clock *kc = READ_ONCE(timer->kclock);
timer_t timer_id = READ_ONCE(timer->it_id);
/* Prevent kfree(timer) after dropping the lock */
@@ -835,8 +829,7 @@ static struct k_itimer *timer_wait_running(struct k_itimer *timer,
* kc->timer_wait_running() might drop RCU lock. So @timer
* cannot be touched anymore after the function returns!
*/
- if (!WARN_ON_ONCE(!kc->timer_wait_running))
- kc->timer_wait_running(timer);
+ timer->kclock->timer_wait_running(timer);
rcu_read_unlock();
/* Relock the timer. It might be not longer hashed. */
@@ -899,7 +892,6 @@ static int do_timer_settime(timer_t timer_id, int tmr_flags,
struct itimerspec64 *new_spec64,
struct itimerspec64 *old_spec64)
{
- const struct k_clock *kc;
struct k_itimer *timr;
unsigned long flags;
int error;
@@ -922,11 +914,7 @@ retry:
/* Prevent signal delivery and rearming. */
timr->it_signal_seq++;
- kc = timr->kclock;
- if (WARN_ON_ONCE(!kc || !kc->timer_set))
- error = -EINVAL;
- else
- error = kc->timer_set(timr, tmr_flags, new_spec64, old_spec64);
+ error = timr->kclock->timer_set(timr, tmr_flags, new_spec64, old_spec64);
if (error == TIMER_RETRY) {
// We already got the old time...
@@ -1008,18 +996,6 @@ static inline void posix_timer_cleanup_ignored(struct k_itimer *tmr)
}
}
-static inline int timer_delete_hook(struct k_itimer *timer)
-{
- const struct k_clock *kc = timer->kclock;
-
- /* Prevent signal delivery and rearming. */
- timer->it_signal_seq++;
-
- if (WARN_ON_ONCE(!kc || !kc->timer_del))
- return -EINVAL;
- return kc->timer_del(timer);
-}
-
/* Delete a POSIX.1b interval timer. */
SYSCALL_DEFINE1(timer_delete, timer_t, timer_id)
{
@@ -1032,7 +1008,10 @@ retry_delete:
if (!timer)
return -EINVAL;
- if (unlikely(timer_delete_hook(timer) == TIMER_RETRY)) {
+ /* Prevent signal delivery and rearming. */
+ timer->it_signal_seq++;
+
+ if (unlikely(timer->kclock->timer_del(timer) == TIMER_RETRY)) {
/* Unlocks and relocks the timer if it still exists */
timer = timer_wait_running(timer, &flags);
goto retry_delete;
@@ -1078,7 +1057,7 @@ retry_delete:
* mechanism. Worse, that timer mechanism might run the expiry
* function concurrently.
*/
- if (timer_delete_hook(timer) == TIMER_RETRY) {
+ if (timer->kclock->timer_del(timer) == TIMER_RETRY) {
/*
* Timer is expired concurrently, prevent livelocks
* and pointless spinning on RT.
next prev parent reply other threads:[~2025-03-13 11:31 UTC|newest]
Thread overview: 68+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-08 16:48 [patch V3 00/18] posix-timers: Rework the global hash table and provide a sane mechanism for CRIU Thomas Gleixner
2025-03-08 16:48 ` [patch V3 01/18] posix-timers: Ensure that timer initialization is fully visible Thomas Gleixner
2025-03-08 21:39 ` Frederic Weisbecker
2025-03-13 11:31 ` [tip: timers/core] " tip-bot2 for Thomas Gleixner
2025-03-08 16:48 ` [patch V3 02/18] posix-timers: Initialise timer before adding it to the hash table Thomas Gleixner
2025-03-11 13:25 ` Frederic Weisbecker
2025-03-11 14:16 ` Thomas Gleixner
2025-03-13 11:31 ` [tip: timers/core] " tip-bot2 for Eric Dumazet
2025-03-08 16:48 ` [patch V3 03/18] posix-timers: Add cond_resched() to posix_timer_add() search loop Thomas Gleixner
2025-03-13 11:31 ` [tip: timers/core] " tip-bot2 for Eric Dumazet
2025-03-08 16:48 ` [patch V3 04/18] posix-timers: Cleanup includes Thomas Gleixner
2025-03-13 11:31 ` [tip: timers/core] " tip-bot2 for Thomas Gleixner
2025-03-08 16:48 ` [patch V3 05/18] posix-timers: Remove a few paranoid warnings Thomas Gleixner
2025-03-13 11:31 ` tip-bot2 for Thomas Gleixner [this message]
2025-03-08 16:48 ` [patch V3 06/18] posix-timers: Remove SLAB_PANIC from kmem cache Thomas Gleixner
2025-03-13 11:31 ` [tip: timers/core] " tip-bot2 for Thomas Gleixner
2025-03-08 16:48 ` [patch V3 07/18] posix-timers: Use guards in a few places Thomas Gleixner
2025-03-13 11:31 ` [tip: timers/core] " tip-bot2 for Thomas Gleixner
2025-03-08 16:48 ` [patch V3 08/18] posix-timers: Simplify lock/unlock_timer() Thomas Gleixner
2025-03-13 11:31 ` [tip: timers/core] " tip-bot2 for Thomas Gleixner
2025-03-08 16:48 ` [patch V3 09/18] posix-timers: Rework timer removal Thomas Gleixner
2025-03-09 23:17 ` Frederic Weisbecker
2025-03-10 6:33 ` Thomas Gleixner
2025-03-10 8:13 ` [patch V3a " Thomas Gleixner
2025-03-13 11:31 ` [tip: timers/core] " tip-bot2 for Thomas Gleixner
2025-03-08 16:48 ` [patch V3 10/18] posix-timers: Make lock_timer() use guard() Thomas Gleixner
2025-03-10 11:57 ` Frederic Weisbecker
2025-03-10 17:36 ` Thomas Gleixner
2025-03-10 22:16 ` Frederic Weisbecker
2025-03-13 11:31 ` [tip: timers/core] " tip-bot2 for Peter Zijlstra
2025-03-08 16:48 ` [patch V3 11/18] posix-timers: Make signal_struct:: Next_posix_timer_id an atomic_t Thomas Gleixner
2025-03-10 22:57 ` Frederic Weisbecker
2025-03-11 13:41 ` Frederic Weisbecker
2025-03-13 11:31 ` [tip: timers/core] " tip-bot2 for Eric Dumazet
2025-03-08 16:48 ` [patch V3 12/18] posix-timers: Improve hash table performance Thomas Gleixner
2025-03-11 13:44 ` Frederic Weisbecker
2025-03-13 11:31 ` [tip: timers/core] " tip-bot2 for Thomas Gleixner
2025-03-08 16:48 ` [patch V3 13/18] posix-timers: Switch to jhash32() Thomas Gleixner
2025-03-13 11:31 ` [tip: timers/core] " tip-bot2 for Thomas Gleixner
2025-03-08 16:48 ` [patch V3 14/18] posix-timers: Avoid false cacheline sharing Thomas Gleixner
2025-03-11 13:53 ` Frederic Weisbecker
2025-03-13 11:31 ` [tip: timers/core] " tip-bot2 for Thomas Gleixner
2025-03-13 22:13 ` [patch V3 14/18] " David Laight
2025-03-17 6:20 ` Nysal Jan K.A.
2025-03-08 16:48 ` [patch V3 15/18] posix-timers: Make per process list RCU safe Thomas Gleixner
2025-03-11 15:29 ` Frederic Weisbecker
2025-03-13 11:31 ` [tip: timers/core] " tip-bot2 for Thomas Gleixner
2025-03-08 16:48 ` [patch V3 16/18] posix-timers: Dont iterate /proc/$PID/timers with sighand:: Siglock held Thomas Gleixner
2025-03-08 22:38 ` Cyrill Gorcunov
2025-03-11 15:26 ` Frederic Weisbecker
2025-03-13 11:31 ` [tip: timers/core] " tip-bot2 for Thomas Gleixner
2025-03-08 16:48 ` [patch V3 17/18] posix-timers: Provide a mechanism to allocate a given timer ID Thomas Gleixner
2025-03-08 22:25 ` Cyrill Gorcunov
2025-03-11 21:35 ` Frederic Weisbecker
2025-03-11 22:05 ` Thomas Gleixner
2025-03-11 22:07 ` [patch V3a " Thomas Gleixner
2025-03-11 22:32 ` Frederic Weisbecker
2025-03-12 7:56 ` Cyrill Gorcunov
2025-03-12 11:24 ` Thomas Gleixner
2025-03-12 11:31 ` Thomas Gleixner
2025-03-12 12:41 ` Cyrill Gorcunov
2025-03-12 17:45 ` Thomas Gleixner
2025-03-13 11:31 ` [tip: timers/core] " tip-bot2 for Thomas Gleixner
2025-03-12 12:59 ` [patch V3 17/18] " Cyrill Gorcunov
2025-03-08 16:48 ` [patch V3 18/18] selftests/timers/posix-timers: Add a test for exact allocation mode Thomas Gleixner
2025-03-10 8:11 ` [patch V3a " Thomas Gleixner
2025-03-11 21:44 ` Frederic Weisbecker
2025-03-13 11:31 ` [tip: timers/core] " tip-bot2 for Thomas Gleixner
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=174186549209.14745.2321427735841251654.tip-bot2@tip-bot2 \
--to=tip-bot2@linutronix.de \
--cc=frederic@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=x86@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®