From: <gregkh@linuxfoundation.org>
To: Julia.Lawall@inria.fr,aha310510@gmail.com,akpm@linux-foundation.org,anna-maria@linutronix.de,arnd@arndb.de,gregkh@linuxfoundation.org,jacob.e.keller@intel.com,linux-staging@lists.linux.dev,linux@roeck-us.net,luiz.dentz@gmail.com,marcel@holtmann.org,maz@kernel.org,peterz@infradead.org,rostedt@goodmis.org,sboyd@kernel.org,tglx@linutronix.de,viresh.kumar@linaro.org
Cc: <stable-commits@vger.kernel.org>
Subject: Patch "Documentation: Remove bogus claim about del_timer_sync()" has been added to the 5.15-stable tree
Date: Sat, 07 Feb 2026 16:43:01 +0100 [thread overview]
Message-ID: <2026020701-navigate-handyman-9662@gregkh> (raw)
In-Reply-To: <20251128160539.358938-2-aha310510@gmail.com>
This is a note to let you know that I've just added the patch titled
Documentation: Remove bogus claim about del_timer_sync()
to the 5.15-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
The filename of the patch is:
documentation-remove-bogus-claim-about-del_timer_sync.patch
and it can be found in the queue-5.15 subdirectory.
If you, or anyone else, feels it should not be added to the stable tree,
please let <stable@vger.kernel.org> know about it.
From stable+bounces-197603-greg=kroah.com@vger.kernel.org Fri Nov 28 17:06:29 2025
From: Jeongjun Park <aha310510@gmail.com>
Date: Sat, 29 Nov 2025 01:05:26 +0900
Subject: Documentation: Remove bogus claim about del_timer_sync()
To: stable@vger.kernel.org
Cc: gregkh@linuxfoundation.org, tglx@linutronix.de, Julia.Lawall@inria.fr, akpm@linux-foundation.org, anna-maria@linutronix.de, arnd@arndb.de, linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org, linux@roeck-us.net, luiz.dentz@gmail.com, marcel@holtmann.org, maz@kernel.org, peterz@infradead.org, rostedt@goodmis.org, sboyd@kernel.org, viresh.kumar@linaro.org, aha310510@gmail.com, linux-staging@lists.linux.dev, Jacob Keller <jacob.e.keller@intel.com>
Message-ID: <20251128160539.358938-2-aha310510@gmail.com>
From: Thomas Gleixner <tglx@linutronix.de>
[ Upstream commit b0b0aa5d858d4d2fe39a5e4486e0550e858108f6 ]
del_timer_sync() does not return the number of times it tried to delete the
timer which rearms itself. It's clearly documented:
The function returns whether it has deactivated a pending timer or not.
This part of the documentation is from 2003 where del_timer_sync() really
returned the number of deletion attempts for unknown reasons. The code
was rewritten in 2005, but the documentation was not updated.
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Reviewed-by: Jacob Keller <jacob.e.keller@intel.com>
Reviewed-by: Anna-Maria Behnsen <anna-maria@linutronix.de>
Link: https://lore.kernel.org/r/20221123201624.452282769@linutronix.de
Signed-off-by: Jeongjun Park <aha310510@gmail.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
---
Documentation/kernel-hacking/locking.rst | 3 +--
Documentation/translations/it_IT/kernel-hacking/locking.rst | 4 +---
2 files changed, 2 insertions(+), 5 deletions(-)
--- a/Documentation/kernel-hacking/locking.rst
+++ b/Documentation/kernel-hacking/locking.rst
@@ -1009,8 +1009,7 @@ Another common problem is deleting timer
calling add_timer() at the end of their timer function).
Because this is a fairly common case which is prone to races, you should
use del_timer_sync() (``include/linux/timer.h``) to
-handle this case. It returns the number of times the timer had to be
-deleted before we finally stopped it from adding itself back in.
+handle this case.
Locking Speed
=============
--- a/Documentation/translations/it_IT/kernel-hacking/locking.rst
+++ b/Documentation/translations/it_IT/kernel-hacking/locking.rst
@@ -1035,9 +1035,7 @@ Un altro problema è l'eliminazione dei
da soli (chiamando add_timer() alla fine della loro esecuzione).
Dato che questo è un problema abbastanza comune con una propensione
alle corse critiche, dovreste usare del_timer_sync()
-(``include/linux/timer.h``) per gestire questo caso. Questa ritorna il
-numero di volte che il temporizzatore è stato interrotto prima che
-fosse in grado di fermarlo senza che si riavviasse.
+(``include/linux/timer.h``) per gestire questo caso.
Velocità della sincronizzazione
===============================
Patches currently in stable-queue which might be from aha310510@gmail.com are
queue-5.15/timers-update-the-documentation-to-reflect-on-the-new-timer_shutdown-api.patch
queue-5.15/clocksource-drivers-arm_arch_timer-do-not-use-timer-namespace-for-timer_shutdown-function.patch
queue-5.15/timers-split-del_timer-to-prepare-for-shutdown-mode.patch
queue-5.15/arm-spear-do-not-use-timer-namespace-for-timer_shutdown-function.patch
queue-5.15/timers-add-shutdown-mechanism-to-the-internal-functions.patch
queue-5.15/timers-provide-timer_shutdown.patch
queue-5.15/timers-rename-del_timer-to-timer_delete.patch
queue-5.15/timers-replace-bug_on-s.patch
queue-5.15/bluetooth-hci_qca-fix-the-teardown-problem-for-real.patch
queue-5.15/documentation-replace-del_timer-del_timer_sync.patch
queue-5.15/documentation-remove-bogus-claim-about-del_timer_sync.patch
queue-5.15/timers-silently-ignore-timers-with-a-null-function.patch
queue-5.15/timers-get-rid-of-del_singleshot_timer_sync.patch
queue-5.15/clocksource-drivers-sp804-do-not-use-timer-namespace-for-timer_shutdown-function.patch
next prev parent reply other threads:[~2026-02-07 15:43 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-28 16:05 [PATCH 5.15.y 00/14] timers: Provide timer_shutdown[_sync]() Jeongjun Park
2025-11-28 16:05 ` [PATCH 5.15.y 01/14] Documentation: Remove bogus claim about del_timer_sync() Jeongjun Park
2026-02-07 15:43 ` gregkh [this message]
2025-11-28 16:05 ` [PATCH 5.15.y 02/14] ARM: spear: Do not use timer namespace for timer_shutdown() function Jeongjun Park
2026-02-07 15:42 ` Patch "ARM: spear: Do not use timer namespace for timer_shutdown() function" has been added to the 5.15-stable tree gregkh
2025-11-28 16:05 ` [PATCH 5.15.y 03/14] clocksource/drivers/arm_arch_timer: Do not use timer namespace for timer_shutdown() function Jeongjun Park
2026-02-07 15:43 ` Patch "clocksource/drivers/arm_arch_timer: Do not use timer namespace for timer_shutdown() function" has been added to the 5.15-stable tree gregkh
2025-11-28 16:05 ` [PATCH 5.15.y 04/14] clocksource/drivers/sp804: Do not use timer namespace for timer_shutdown() function Jeongjun Park
2026-02-07 15:43 ` Patch "clocksource/drivers/sp804: Do not use timer namespace for timer_shutdown() function" has been added to the 5.15-stable tree gregkh
2025-11-28 16:05 ` [PATCH 5.15.y 05/14] timers: Get rid of del_singleshot_timer_sync() Jeongjun Park
2026-02-07 15:43 ` Patch "timers: Get rid of del_singleshot_timer_sync()" has been added to the 5.15-stable tree gregkh
2025-11-28 16:05 ` [PATCH 5.15.y 06/14] timers: Replace BUG_ON()s Jeongjun Park
2026-02-07 15:43 ` Patch "timers: Replace BUG_ON()s" has been added to the 5.15-stable tree gregkh
2025-11-28 16:05 ` [PATCH 5.15.y 07/14] timers: Rename del_timer() to timer_delete() Jeongjun Park
2026-02-07 15:43 ` Patch "timers: Rename del_timer() to timer_delete()" has been added to the 5.15-stable tree gregkh
2025-11-28 16:05 ` [PATCH 5.15.y 08/14] Documentation: Replace del_timer/del_timer_sync() Jeongjun Park
2026-02-07 15:43 ` Patch "Documentation: Replace del_timer/del_timer_sync()" has been added to the 5.15-stable tree gregkh
2025-11-28 16:05 ` [PATCH 5.15.y 09/14] timers: Silently ignore timers with a NULL function Jeongjun Park
2026-02-07 15:43 ` Patch "timers: Silently ignore timers with a NULL function" has been added to the 5.15-stable tree gregkh
2025-11-28 16:05 ` [PATCH 5.15.y 10/14] timers: Split [try_to_]del_timer[_sync]() to prepare for shutdown mode Jeongjun Park
2026-02-07 15:43 ` Patch "timers: Split [try_to_]del_timer[_sync]() to prepare for shutdown mode" has been added to the 5.15-stable tree gregkh
2025-11-28 16:05 ` [PATCH 5.15.y 11/14] timers: Add shutdown mechanism to the internal functions Jeongjun Park
2026-02-07 15:43 ` Patch "timers: Add shutdown mechanism to the internal functions" has been added to the 5.15-stable tree gregkh
2025-11-28 16:05 ` [PATCH 5.15.y 12/14] timers: Provide timer_shutdown[_sync]() Jeongjun Park
2026-02-07 15:43 ` Patch "timers: Provide timer_shutdown[_sync]()" has been added to the 5.15-stable tree gregkh
2025-11-28 16:05 ` [PATCH 5.15.y 13/14] timers: Update the documentation to reflect on the new timer_shutdown() API Jeongjun Park
2026-02-07 15:43 ` Patch "timers: Update the documentation to reflect on the new timer_shutdown() API" has been added to the 5.15-stable tree gregkh
2025-11-28 16:05 ` [PATCH 5.15.y 14/14] Bluetooth: hci_qca: Fix the teardown problem for real Jeongjun Park
2026-02-07 15:43 ` Patch "Bluetooth: hci_qca: Fix the teardown problem for real" has been added to the 5.15-stable tree gregkh
2026-02-07 15:42 ` [PATCH 5.15.y 00/14] timers: Provide timer_shutdown[_sync]() Greg KH
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=2026020701-navigate-handyman-9662@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=Julia.Lawall@inria.fr \
--cc=aha310510@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=anna-maria@linutronix.de \
--cc=arnd@arndb.de \
--cc=jacob.e.keller@intel.com \
--cc=linux-staging@lists.linux.dev \
--cc=linux@roeck-us.net \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=maz@kernel.org \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=sboyd@kernel.org \
--cc=stable-commits@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=viresh.kumar@linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.