From: Greg KH <gregkh@linuxfoundation.org>
To: Jeongjun Park <aha310510@gmail.com>
Cc: stable@vger.kernel.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, zouyipeng@huawei.com,
linux-staging@lists.linux.dev
Subject: Re: [PATCH 5.10.y 00/15] timers: Provide timer_shutdown[_sync]()
Date: Thu, 23 Apr 2026 14:49:38 +0200 [thread overview]
Message-ID: <2026042355-blighted-chewing-5e50@gregkh> (raw)
In-Reply-To: <20260219171310.118170-1-aha310510@gmail.com>
On Fri, Feb 20, 2026 at 02:12:55AM +0900, Jeongjun Park wrote:
> The "timers: Provide timer_shutdown[_sync]()" patch series implemented a
> useful feature that addresses various bugs caused by attempts to rearm
> shutdown timers.
>
> https://lore.kernel.org/all/20221123201306.823305113@linutronix.de/
>
> However, this patch series was not fully backported to versions prior to
> 6.2, requiring separate patches for older kernels if these bugs were
> encountered.
>
> The biggest problem with this is that even if these bugs were discovered
> and patched in the upstream kernel, if the maintainer or author didn't
> create a separate backport patch for versions prior to 6.2, the bugs would
> remain untouched in older kernels.
>
> Therefore, to reduce the hassle of having to write a separate patch, we
> should backport the remaining unbackported commits from the
> "timers: Provide timer_shutdown[_sync]()" patch series to versions prior
> to 6.2.
>
> ---
> Documentation/RCU/Design/Requirements/Requirements.rst | 2 +-
> Documentation/core-api/local_ops.rst | 2 +-
> Documentation/kernel-hacking/locking.rst | 17 ++---
> Documentation/timers/hrtimers.rst | 2 +-
> Documentation/translations/it_IT/kernel-hacking/locking.rst | 14 ++---
> arch/arm/mach-spear/time.c | 8 +--
> drivers/bluetooth/hci_qca.c | 10 ++-
> drivers/char/tpm/tpm-dev-common.c | 4 +-
> drivers/clocksource/arm_arch_timer.c | 12 ++--
> drivers/clocksource/timer-sp804.c | 6 +-
> drivers/staging/wlan-ng/hfa384x_usb.c | 4 +-
> drivers/staging/wlan-ng/prism2usb.c | 6 +-
> include/linux/timer.h | 17 ++++-
> kernel/time/timer.c | 316 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++-----------------
> net/sunrpc/xprt.c | 2 +-
> 15 files changed, 322 insertions(+), 100 deletions(-)
>
Ugh, I got the following build error for this series:
../drivers/misc/sgi-xp/xpc_partition.c: In function 'xpc_partition_disengaged':
../drivers/misc/sgi-xp/xpc_partition.c:294:25: error: implicit declaration of function 'del_singleshot_timer_sync' [-Werror=implicit-function-declaration]
294 | del_singleshot_timer_sync(&part->disengage_timer);
| ^~~~~~~~~~~~~~~~~~~~~~~~~
Don't know what happened, but I'll go and drop them all now.
Do you _REALLY_ need these in the 5.10.y kernel? Who is going to use
them?
thanks,
greg k-h
next prev parent reply other threads:[~2026-04-23 12:49 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-19 17:12 [PATCH 5.10.y 00/15] timers: Provide timer_shutdown[_sync]() Jeongjun Park
2026-02-19 17:12 ` [PATCH 5.10.y 01/15] Documentation: Remove bogus claim about del_timer_sync() Jeongjun Park
2026-04-23 12:35 ` Patch "Documentation: Remove bogus claim about del_timer_sync()" has been added to the 5.10-stable tree gregkh
2026-02-19 17:12 ` [PATCH 5.10.y 02/15] ARM: spear: Do not use timer namespace for timer_shutdown() function Jeongjun Park
2026-04-23 12:35 ` Patch "ARM: spear: Do not use timer namespace for timer_shutdown() function" has been added to the 5.10-stable tree gregkh
2026-02-19 17:12 ` [PATCH 5.10.y 03/15] clocksource/drivers/arm_arch_timer: Do not use timer namespace for timer_shutdown() function Jeongjun Park
2026-04-23 12:35 ` Patch "clocksource/drivers/arm_arch_timer: Do not use timer namespace for timer_shutdown() function" has been added to the 5.10-stable tree gregkh
2026-02-19 17:12 ` [PATCH 5.10.y 04/15] clocksource/drivers/sp804: Do not use timer namespace for timer_shutdown() function Jeongjun Park
2026-04-23 12:35 ` Patch "clocksource/drivers/sp804: Do not use timer namespace for timer_shutdown() function" has been added to the 5.10-stable tree gregkh
2026-02-19 17:13 ` [PATCH 5.10.y 05/15] timers: Get rid of del_singleshot_timer_sync() Jeongjun Park
2026-04-23 12:35 ` Patch "timers: Get rid of del_singleshot_timer_sync()" has been added to the 5.10-stable tree gregkh
2026-02-19 17:13 ` [PATCH 5.10.y 06/15] timers: Replace BUG_ON()s Jeongjun Park
2026-04-23 12:35 ` Patch "timers: Replace BUG_ON()s" has been added to the 5.10-stable tree gregkh
2026-02-19 17:13 ` [PATCH 5.10.y 07/15] timers: Rename del_timer() to timer_delete() Jeongjun Park
2026-04-23 12:35 ` Patch "timers: Rename del_timer() to timer_delete()" has been added to the 5.10-stable tree gregkh
2026-02-19 17:13 ` [PATCH 5.10.y 08/15] Documentation: Replace del_timer/del_timer_sync() Jeongjun Park
2026-04-23 12:35 ` Patch "Documentation: Replace del_timer/del_timer_sync()" has been added to the 5.10-stable tree gregkh
2026-02-19 17:13 ` [PATCH 5.10.y 09/15] timers: Silently ignore timers with a NULL function Jeongjun Park
2026-04-23 12:35 ` Patch "timers: Silently ignore timers with a NULL function" has been added to the 5.10-stable tree gregkh
2026-02-19 17:13 ` [PATCH 5.10.y 10/15] timers: Split [try_to_]del_timer[_sync]() to prepare for shutdown mode Jeongjun Park
2026-04-23 12:35 ` Patch "timers: Split [try_to_]del_timer[_sync]() to prepare for shutdown mode" has been added to the 5.10-stable tree gregkh
2026-02-19 17:13 ` [PATCH 5.10.y 11/15] timers: Add shutdown mechanism to the internal functions Jeongjun Park
2026-04-23 12:35 ` Patch "timers: Add shutdown mechanism to the internal functions" has been added to the 5.10-stable tree gregkh
2026-02-19 17:13 ` [PATCH 5.10.y 12/15] timers: Provide timer_shutdown[_sync]() Jeongjun Park
2026-04-23 12:35 ` Patch "timers: Provide timer_shutdown[_sync]()" has been added to the 5.10-stable tree gregkh
2026-02-19 17:13 ` [PATCH 5.10.y 13/15] timers: Update the documentation to reflect on the new timer_shutdown() API Jeongjun Park
2026-04-23 12:35 ` Patch "timers: Update the documentation to reflect on the new timer_shutdown() API" has been added to the 5.10-stable tree gregkh
2026-02-19 17:13 ` [PATCH 5.10.y 14/15] Bluetooth: hci_qca: Fix the teardown problem for real Jeongjun Park
2026-04-23 12:35 ` Patch "Bluetooth: hci_qca: Fix the teardown problem for real" has been added to the 5.10-stable tree gregkh
2026-02-19 17:13 ` [PATCH 5.10.y 15/15] timers: Fix NULL function pointer race in timer_shutdown_sync() Jeongjun Park
2026-02-19 17:17 ` Jeongjun Park
2026-04-23 12:35 ` Patch "timers: Fix NULL function pointer race in timer_shutdown_sync()" has been added to the 5.10-stable tree gregkh
2026-04-23 12:49 ` Greg KH [this message]
2026-04-23 13:36 ` [PATCH 5.10.y 00/15] timers: Provide timer_shutdown[_sync]() Jeongjun Park
2026-04-23 13:43 ` Greg KH
2026-04-23 14:07 ` Jeongjun Park
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=2026042355-blighted-chewing-5e50@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=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=viresh.kumar@linaro.org \
--cc=zouyipeng@huawei.com \
/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