linux-kernel - Re: [patch 1/2] add ALL_CPUS option to stop_machine

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: <20080229191559.GA18339@elte.hu>
Date:	Fri, 29 Feb 2008 20:15:59 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Max Krasnyanskiy <maxk@...lcomm.com>
Cc:	Jason Baron <jbaron@...hat.com>,
	Mathieu Desnoyers <mathieu.desnoyers@...ymtl.ca>,
	akpm@...ux-foundation.org, linux-kernel@...r.kernel.org,
	Rusty Russell <rusty@...tcorp.com.au>,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>
Subject: Re: [patch 1/2] add ALL_CPUS option to stop_machine_run()

* Max Krasnyanskiy <maxk@...lcomm.com> wrote:

> btw Being an RT guy you do not think that stop machine is evil ? [...]

i'm not "an RT guy", -rt is just one of the many projects i've been 
involved with.

and no, i dont think stop machine is "evil" - it's currently the best 
way to do certain things. If you can solve it better then sure, i'm 
awaiting your patches - but the only patch i saw from you so far was the 
one that turned off stop-machine for isolated cpus - which was 
incredibly broken and ignored the problem altogether.

Right now the answer is: "if you want to do hard RT then avoid doing 
things like loading modules". (which you should avoid while doing 
hard-RT anyway)

	Ingo
--
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/