linux-kernel - Re: [PATCH 03/15] sched/fair: Add lag based placement

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20250207-convivial-silver-chachalaca-fc0fba@leitao>
Date: Fri, 7 Feb 2025 05:22:01 -0800
From: Breno Leitao <leitao@...ian.org>
To: Peter Zijlstra <peterz@...radead.org>
Cc: mingo@...nel.org, vincent.guittot@...aro.org,
	linux-kernel@...r.kernel.org, juri.lelli@...hat.com,
	dietmar.eggemann@....com, rostedt@...dmis.org, bsegall@...gle.com,
	mgorman@...e.de, bristot@...hat.com, corbet@....net,
	qyousef@...alina.io, chris.hyser@...cle.com,
	patrick.bellasi@...bug.net, pjt@...gle.com, pavel@....cz,
	qperret@...gle.com, tim.c.chen@...ux.intel.com, joshdon@...gle.com,
	timj@....org, kprateek.nayak@....com, yu.c.chen@...el.com,
	youssefesmat@...omium.org, joel@...lfernandes.org, efault@....de,
	tglx@...utronix.de, kernel-team@...a.com
Subject: Re: [PATCH 03/15] sched/fair: Add lag based placement

On Fri, Feb 07, 2025 at 01:30:20PM +0100, Peter Zijlstra wrote:
> On Fri, Feb 07, 2025 at 04:25:02AM -0800, Breno Leitao wrote:
> 
> > I haven't seen this patch in stable. Is it queue up for the next
> > submission for stable?
> 
> It's not yet queued, up. I meant to do that this week, but 'stuff' kept
> getting in between. I'll try and get it pushed into tip/sched/urgent
> this seekend somewhere -- but it is unlikely to make -rc2 at this pace.

That is fine.  I just want to assure that this patch will eventually get
to stable, so, I don't need to carry forward this patch forever in my
production tree.

I will let in ~week if we are still seeing this warning in our machines.

Thanks for the quick response,
--breno