mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Sasha Levin <sashal@kernel.org>
Cc: Borislav Petkov <bp@alien8.de>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	x86-ml <x86@kernel.org>, lkml <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] sched/urgent for v6.13-rc3
Date: Sat, 14 Dec 2024 19:05:37 +0100	[thread overview]
Message-ID: <20241214180537.GA10560@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <Z13BzesSJDSuSXRc@lappy>

On Sat, Dec 14, 2024 at 12:36:07PM -0500, Sasha Levin wrote:
> On Mon, Dec 09, 2024 at 10:48:22AM +0100, Borislav Petkov wrote:
> > Hi Linus,
> > 
> > please pull the sched/urgent lineup for v6.13-rc3.
> 
> Hey Boris,
> 
> I'm a bit late to this party, but I've started seeing the following
> warning. I'm not 100% sure that this PR is the culprit because Linus
> ended up pulling it before I could run tests on it, but I haven't seen
> this warning before.
> 
> [ 1107.003243] ------------[ cut here ]------------
> [ 1107.010677] WARNING: CPU: 0 PID: 16 at kernel/sched/deadline.c:1995 enqueue_dl_entity+0x4a8/0x570

Ah, yeah, no. That's a known issue which we *finally* managed to track
down last week. Unfortunately this sched/urgent pull does not yet
include those patches.

If you want them, they can be had here:

  git://git.kernel.org/pub/scm/linux/kernel/git/peterz/queue.git sched/urgent

I was meaning to push them to tip/sched/urgent on Monday, so they'd be
in next week's batch.

But if people want them now, have at :-)

  parent reply	other threads:[~2024-12-14 18:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-09  9:48 Borislav Petkov
2024-12-09 18:38 ` pr-tracker-bot
2024-12-14 17:36 ` Sasha Levin
2024-12-14 17:52   ` Borislav Petkov
2024-12-14 18:05   ` Peter Zijlstra [this message]
2024-12-14 18:32     ` Peter Zijlstra
2024-12-15 18:45     ` pr-tracker-bot

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=20241214180537.GA10560@noisy.programming.kicks-ass.net \
    --to=peterz@infradead.org \
    --cc=bp@alien8.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sashal@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 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®