public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
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,
	linux-staging@lists.linux.dev
Subject: Re: [PATCH 5.15.y 00/14] timers: Provide timer_shutdown[_sync]()
Date: Sat, 7 Feb 2026 16:42:15 +0100	[thread overview]
Message-ID: <2026020754-boxing-tug-de15@gregkh> (raw)
In-Reply-To: <20251128160539.358938-1-aha310510@gmail.com>

On Sat, Nov 29, 2025 at 01:05:25AM +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.

You forgot to include commit 20739af07383 ("timers: Fix NULL function
pointer race in timer_shutdown_sync()") in this series.  I've now taken
them all, let's see how it goes!

thanks,

greg k-h

      parent reply	other threads:[~2026-02-07 15:42 UTC|newest]

Thread overview: 16+ 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
2025-11-28 16:05 ` [PATCH 5.15.y 02/14] ARM: spear: Do not use timer namespace for timer_shutdown() function Jeongjun Park
2025-11-28 16:05 ` [PATCH 5.15.y 03/14] clocksource/drivers/arm_arch_timer: " Jeongjun Park
2025-11-28 16:05 ` [PATCH 5.15.y 04/14] clocksource/drivers/sp804: " Jeongjun Park
2025-11-28 16:05 ` [PATCH 5.15.y 05/14] timers: Get rid of del_singleshot_timer_sync() Jeongjun Park
2025-11-28 16:05 ` [PATCH 5.15.y 06/14] timers: Replace BUG_ON()s Jeongjun Park
2025-11-28 16:05 ` [PATCH 5.15.y 07/14] timers: Rename del_timer() to timer_delete() Jeongjun Park
2025-11-28 16:05 ` [PATCH 5.15.y 08/14] Documentation: Replace del_timer/del_timer_sync() Jeongjun Park
2025-11-28 16:05 ` [PATCH 5.15.y 09/14] timers: Silently ignore timers with a NULL function Jeongjun Park
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
2025-11-28 16:05 ` [PATCH 5.15.y 11/14] timers: Add shutdown mechanism to the internal functions Jeongjun Park
2025-11-28 16:05 ` [PATCH 5.15.y 12/14] timers: Provide timer_shutdown[_sync]() Jeongjun Park
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
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:42 ` Greg KH [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=2026020754-boxing-tug-de15@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 \
    /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