linux-kernel - Re: [PATCH 00/48] percpu: Consistent per cpu operations V4

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: <alpine.DEB.2.10.1403042127330.3742@nuc>
Date:	Tue, 4 Mar 2014 21:29:43 -0600 (CST)
From:	Christoph Lameter <cl@...ux.com>
To:	Andrew Morton <akpm@...ux-foundation.org>
cc:	Tejun Heo <tj@...nel.org>, akpm@...uxfoundation.org,
	rostedt@...dmis.org, linux-kernel@...r.kernel.org,
	Ingo Molnar <mingo@...nel.org>,
	Peter Zijlstra <peterz@...radead.org>,
	Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [PATCH 00/48] percpu: Consistent per cpu operations V4

On Tue, 4 Mar 2014, Andrew Morton wrote:

> This series is structured as
>
> [patch 1]: make changes whcih trigger lots of runtime warnings
> [patch 2-n]: fix up those warnings
>
> yes?

Nope. The warning causing things are eliminated before the checks are
introduced. The first patch adds new functionality. The following patches
fix warnings that will otherwise spew over the logs and then we add the
checks.

> So we're proposing adding a 48-patch bisection hole in which scary
> warnings will be emitted.

That is not the case.

What could occur is that there could be kernel configurations which
trigger warnings that so far have not been tested.


> In linux-next arch/arm/mach-msm/timer.c gets moved to
> drivers/clocksource/qcom-timer.c, which I fixed up.  Apart from that it
> all still merges OK...

Great.

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