linux-kernel - Re: [pchecks v2 2/2] percpu: Add preemption checks to __this

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: <0000014179b908eb-29821dc1-7b08-4dd5-b86b-a88c00864249-000000@email.amazonses.com>
Date:	Wed, 2 Oct 2013 15:11:12 +0000
From:	Christoph Lameter <cl@...ux.com>
To:	Ingo Molnar <mingo@...nel.org>
cc:	Tejun Heo <tj@...nel.org>, akpm@...uxfoundation.org,
	linux-arch@...r.kernel.org, Steven Rostedt <srostedt@...hat.com>,
	linux-kernel@...r.kernel.org,
	Peter Zijlstra <peterz@...radead.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>
Subject: Re: [pchecks v2 2/2] percpu: Add preemption checks to __this_cpu
 ops

On Sat, 28 Sep 2013, Ingo Molnar wrote:

>
> * Christoph Lameter <cl@...ux.com> wrote:
>
> > On Wed, 25 Sep 2013, Ingo Molnar wrote:
> >
> > > >
> > > > I think this is necessary since it seems that the discussions on how
> > > > to do the raw_cpu conversions may take some time. If we enable it by
> > > > default then there will be numerous new log messages. That way a
> > > > developer can enable it for working on this.
> > >
> > > Note that for these patches to be eligible for upstream merge any
> > > extra warnings that trigger must be fixed, regardless of the default
> > > setting.
> >
> > That is exactly what this patch does. There will only be warning if the
> > user enabled them.
>
> You didn't understand me apparently: all warnings that trigger with the
> debug CONFIG option enabled must be fixed before this can be sent
> upstream.

This patchset is required to determine the warnings that will be triggered
and to get the work to address these issues done. The feedback so far
indicates that there may be lots of discussions regarding the warnings
that have been discovered so far. Its not realistic to do this in one go.




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