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: <00000142be7e005c-7ec3b0da-e975-438e-9203-7fa7ed80c891-000000@email.amazonses.com>
Date:	Wed, 4 Dec 2013 16:43:18 +0000
From:	Christoph Lameter <cl@...ux.com>
To:	Ingo Molnar <mingo@...nel.org>
cc:	Tejun Heo <tj@...nel.org>, akpm@...uxfoundation.org,
	rostedt@...dmis.org, linux-kernel@...r.kernel.org,
	Peter Zijlstra <peterz@...radead.org>,
	Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [PATCH 00/41] percpu: Consistent per cpu operations V1

On Wed, 4 Dec 2013, Ingo Molnar wrote:

>
> * Christoph Lameter <cl@...ux.com> wrote:
>
> > The kernel has never been audited to ensure that this_cpu operations
> > are consistently used throughout the kernel. The code generated in
> > many places can be improved through the use of this_cpu operations
> > (which uses a segment register for relocation of per cpu offsets
> > instead of performing address calculations).
>
> Your series lacks the this_cpu ops preempt debugging patches that you
> worked on before, what happened to them?

They are included. Please read the complete description. Patches 13 14 and
18 implement the preemption checks.

> Those debug facilities caught kernel real bugs and they are thus
> essential before any percpu extension can be done.

Yes please apply the preemptiopn debug patches included in this series
ASAP.

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ