linux-kernel - Re: [PATCH] CPU hotplug: Slow down hotplug operations

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]

Date:	Sun, 11 May 2014 20:48:08 +0200
From:	Borislav Petkov <bp@...en8.de>
To:	Thomas Gleixner <tglx@...utronix.de>
Cc:	Pavel Machek <pavel@....cz>,
	Andrew Morton <akpm@...ux-foundation.org>,
	LKML <linux-kernel@...r.kernel.org>,
	"H. Peter Anvin" <hpa@...or.com>, Ingo Molnar <mingo@...nel.org>,
	Peter Zijlstra <peterz@...radead.org>,
	Mel Gorman <mgorman@...e.com>,
	Steven Rostedt <rostedt@...dmis.org>,
	Mike Galbraith <mgalbraith@...e.de>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	"Srivatsa S. Bhat" <srivatsa.bhat@...ux.vnet.ibm.com>
Subject: Re: [PATCH] CPU hotplug: Slow down hotplug operations

On Sun, May 11, 2014 at 08:29:30PM +0200, Thomas Gleixner wrote:
> On Sun, 11 May 2014, Pavel Machek wrote:
> > Well. If you add the delay, you'll mask real problems and cause regressions when
> > the delay is removed -- because fix-hotplug will probably take time to get right.
> > 
> > Bad idea, AFAICT.
> 
> Agreed, but Boris is right, that the current duct tape hackery needs
> to stop. And the delay was the desperate attempt to wake up people to
> focus on replacing the current mess instead of making it more
> entangled.

I think Pavel is missing the point: the delay will be removed with the
rewrite of cpu hotplug, after it actually works reliably. Then we won't
need delay anyway.

-- 
Regards/Gruss,
    Boris.

Sent from a fat crate under my desk. Formatting is fine.
--
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/