All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Thorsten Leemhuis <regressions@leemhuis.info>
Cc: Thomas Gleixner <tglx@kernel.org>,
	Hanabishi <i.r.e.c.c.a.k.u.n+kernel.org@gmail.com>,
	Eric Naim <dnaim@cachyos.org>,
	stable@vger.kernel.org, linux-tip-commits@vger.kernel.org,
	x86@kernel.org, Linus Torvalds <torvalds@linux-foundation.org>,
	linux-kernel@vger.kernel.org,
	Linux kernel regressions list <regressions@lists.linux.dev>
Subject: Re: [tip: timers/urgent] clockevents: Add missing resets of the next_event_forced flag
Date: Tue, 21 Apr 2026 08:41:17 +0200	[thread overview]
Message-ID: <2026042110-surpass-petite-9551@gregkh> (raw)
In-Reply-To: <bbf8cc92-9ce1-4579-85ac-f90aca4d7858@leemhuis.info>

On Tue, Apr 21, 2026 at 08:26:35AM +0200, Thorsten Leemhuis wrote:
> On 4/21/26 08:18, Thomas Gleixner wrote:
> > On Sun, Apr 19 2026 at 17:11, Linux regression tracking (Thorsten Leemhuis) wrote:
> >> On 4/16/26 21:26, tip-bot2 for Thomas Gleixner wrote:
> >>> The following commit has been merged into the timers/urgent branch of tip:
> >>>
> >>> Commit-ID:     4096fd0e8eaea13ebe5206700b33f49635ae18e5
> >>> Gitweb:        https://git.kernel.org/tip/4096fd0e8eaea13ebe5206700b33f49635ae18e5
> >>> Author:        Thomas Gleixner <tglx@kernel.org>
> >>> AuthorDate:    Tue, 14 Apr 2026 22:55:01 +02:00
> >>> Committer:     Thomas Gleixner <tglx@kernel.org>
> >>> CommitterDate: Thu, 16 Apr 2026 21:22:04 +02:00
> >>>
> >>> clockevents: Add missing resets of the next_event_forced flag
> >>
> >> Just wondering: what's the plan to mainline this? I wonder if this is
> >> worth mainlining rather quickly and the tell the stable team right
> >> afterwards to queue it up for 7.0.1, as in addition to the two affected
> >> people in this thread (one of which stated that "several users from
> >> CachyOS reported this regression as well") I noticed three more 7.0 bug
> >> reports in the past few days that likely are fixed by the quoted patch:
> > 
> > It's in Linus tree and I asked the stable folks to withhold the original
> > patch which it fixes, so they can queue both at once.
> 
> Yeah, I noticed, and many thx! Also many thx for planning the backport,
> this is great. But that "original patch" is already in 7.0, which makes
> me wonder:
> 
> Should we ask Greg (now CCed) to include a backport (once it exists) for
> 7.0.1, even if that is in testing already and might mean that this needs
> another stable-rc or delayed? Because in addition to those three reports
> I mentioned earlier I noticed one more today:
> https://bugzilla.kernel.org/show_bug.cgi?id=221377
> 
> And maybe this is the same issue, too:
> https://bugzilla.kernel.org/show_bug.cgi?id=221388
> 
> IOW: quite a few people are hitting this.

I've already dropped this from all of the other stable queues.  If you
want me to pick up something from linux-next now, for 7.0.1, I'll be
glad to do so, just let me know.

thanks,

greg k-h

  reply	other threads:[~2026-04-21  6:41 UTC|newest]

Thread overview: 66+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-07  8:54 [patch 00/12] hrtimers: Prevent hrtimer interrupt starvation Thomas Gleixner
2026-04-07  8:54 ` [patch 01/12] clockevents: Prevent timer " Thomas Gleixner
2026-04-07  9:42   ` Peter Zijlstra
2026-04-07 11:30     ` Thomas Gleixner
2026-04-07 11:49       ` Peter Zijlstra
2026-04-07 13:59         ` Thomas Gleixner
2026-04-07 14:00   ` Frederic Weisbecker
2026-04-07 16:08     ` Thomas Gleixner
2026-04-07 18:01       ` Thomas Gleixner
2026-04-07 14:33   ` Thomas Gleixner
2026-04-08 12:41   ` Thomas Weißschuh
2026-04-08 13:55     ` Thomas Weißschuh
2026-04-08 15:18       ` Thomas Gleixner
2026-04-08 14:15   ` Frederic Weisbecker
2026-04-10 20:52   ` Nathan Chancellor
2026-04-10 21:02     ` Thomas Gleixner
2026-04-10 21:13       ` Nathan Chancellor
2026-04-13 21:20   ` The "clockevents: Prevent timer interrupt starvation" patch causes lockups Hanabishi
2026-04-14 15:39     ` Eric Naim
2026-04-14 17:25       ` Calvin Owens
2026-04-14 18:19         ` Eric Naim
2026-04-14 18:04       ` Frederic Weisbecker
2026-04-14 18:25         ` Hanabishi
2026-04-14 20:55           ` Thomas Gleixner
2026-04-14 21:35             ` Hanabishi
2026-04-15 13:51               ` Eric Naim
2026-04-16 19:26             ` [tip: timers/urgent] clockevents: Add missing resets of the next_event_forced flag tip-bot2 for Thomas Gleixner
2026-04-19 15:11               ` Linux regression tracking (Thorsten Leemhuis)
2026-04-21  6:18                 ` Thomas Gleixner
2026-04-21  6:26                   ` Thorsten Leemhuis
2026-04-21  6:41                     ` Greg KH [this message]
2026-04-21  6:42                       ` Greg KH
2026-04-07  8:54 ` [patch 02/12] hrtimer: Provide hrtimer_start_range_ns_user() Thomas Gleixner
2026-04-07  9:54   ` Peter Zijlstra
2026-04-07 11:32     ` Thomas Gleixner
2026-04-07  9:57   ` Peter Zijlstra
2026-04-07 11:34     ` Thomas Gleixner
2026-04-07  8:54 ` [patch 03/12] hrtimer: Use hrtimer_start_expires_user() for hrtimer sleepers Thomas Gleixner
2026-04-07  9:59   ` Peter Zijlstra
2026-04-07  8:54 ` [patch 04/12] posix-timers: Expand timer_[re]arm() callbacks with a boolean return value Thomas Gleixner
2026-04-07 10:00   ` Peter Zijlstra
2026-04-07 20:20   ` John Stultz
2026-04-07  8:54 ` [patch 05/12] posix-timers: Handle the timer_[re]arm() " Thomas Gleixner
2026-04-07 10:01   ` Peter Zijlstra
2026-04-07  8:54 ` [patch 06/12] posix-timers: Switch to hrtimer_start_expires_user() Thomas Gleixner
2026-04-07 10:01   ` Peter Zijlstra
2026-04-07  8:54 ` [patch 07/12] alarmtimer: Provide alarmtimer_start() Thomas Gleixner
2026-04-07 10:04   ` Peter Zijlstra
2026-04-07 11:34     ` Thomas Gleixner
2026-04-07 20:23   ` John Stultz
2026-04-07  8:54 ` [patch 08/12] alarmtimer: Convert posix timer functions to alarmtimer_start() Thomas Gleixner
2026-04-07 20:19   ` John Stultz
2026-04-07  8:54 ` [patch 09/12] fs/timerfd: Use the new alarm/hrtimer functions Thomas Gleixner
2026-04-07 10:09   ` Peter Zijlstra
2026-04-07 11:41     ` Thomas Gleixner
2026-04-07  8:55 ` [patch 10/12] power: supply: charger-manager: Switch to alarmtimer_start() Thomas Gleixner
2026-04-07 10:11   ` Peter Zijlstra
2026-04-07  8:55 ` [patch 11/12] netfilter: xt_IDLETIMER: " Thomas Gleixner
2026-04-07  8:55 ` [patch 12/12] alarmtimer: Remove unused interfaces Thomas Gleixner
2026-04-07 20:21   ` John Stultz
2026-04-07 14:43 ` [patch 00/12] hrtimers: Prevent hrtimer interrupt starvation Thomas Gleixner
2026-04-07 16:17   ` Thomas Gleixner
2026-04-07 17:38 ` Calvin Owens
2026-04-07 18:03   ` Thomas Gleixner
2026-04-07 18:35     ` Calvin Owens
2026-04-07 20:58       ` 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=2026042110-surpass-petite-9551@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=dnaim@cachyos.org \
    --cc=i.r.e.c.c.a.k.u.n+kernel.org@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tip-commits@vger.kernel.org \
    --cc=regressions@leemhuis.info \
    --cc=regressions@lists.linux.dev \
    --cc=stable@vger.kernel.org \
    --cc=tglx@kernel.org \
    --cc=torvalds@linux-foundation.org \
    --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 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.