linux-kernel - Re: [RFC PATCH] x86, espfix: use spin

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: <20150514212753.GE29125@pd.tnic>
Date:	Thu, 14 May 2015 23:27:53 +0200
From:	Borislav Petkov <bp@...en8.de>
To:	Ingo Molnar <mingo@...nel.org>
Cc:	Gu Zheng <guz.fnst@...fujitsu.com>,
	"H. Peter Anvin" <hpa@...or.com>,
	Thomas Gleixner <tglx@...utronix.de>,
	linux-kernel@...r.kernel.org, x86@...nel.org
Subject: Re: [RFC PATCH] x86, espfix: use spin_lock rather than mutex

Remove stable@ from CC.

On Thu, May 14, 2015 at 08:29:55PM +0200, Ingo Molnar wrote:
> We could allocate them on the boot CPU side and hand them over to the 
> secondary CPU.

Yeah, something along those lines. I mean, they're allocated and in-use
during the complete system lifetime, we might just as well allocate them
all in one go. Btw, what's our allocator that early, memblock?

Still, what I find strange is why are we seeing this only now? Is it
because it had to be a big box (cpu >= 128) or something else changed...?

Hohumm.

-- 
Regards/Gruss,
    Boris.

ECO tip #101: Trim your mails when you reply.
--
--
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/