[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20241214183210.GB10560@noisy.programming.kicks-ass.net>
Date: Sat, 14 Dec 2024 19:32:10 +0100
From: Peter Zijlstra <peterz@...radead.org>
To: Sasha Levin <sashal@...nel.org>
Cc: Borislav Petkov <bp@...en8.de>,
Linus Torvalds <torvalds@...ux-foundation.org>,
x86-ml <x86@...nel.org>, lkml <linux-kernel@...r.kernel.org>
Subject: Re: [GIT PULL] sched/urgent for v6.13-rc3
On Sat, Dec 14, 2024 at 07:05:37PM +0100, Peter Zijlstra wrote:
> 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.
/me finds that the robots have blessed them and it's only Saturday, so I
could push them into tip now and then they go to Linus tomorrow.
Yep, let me do that.
Powered by blists - more mailing lists