linux-kernel - Re: [patch 0/17] Series to introduce WARN()... a WARN

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]

Date:	Wed, 9 Jul 2008 04:19:56 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	Arjan van de Ven <arjan@...radead.org>,
	linux-kernel@...r.kernel.org
Subject: Re: [patch 0/17] Series to introduce WARN()... a WARN_ON() variant
 that takes printk arguments

On Wed, 9 Jul 2008 12:13:48 +0200 Ingo Molnar <mingo@...e.hu> wrote:

> > Hi,
> > 
> > This patch series introduces WARN(), which is a WARN_ON() variant that 
> > takes printk() like arguments. This was done after both akpm and I hit 
> > several cases where this would have been useful; in addition, with 
> > WARN(), we put the printk string inside the -----[ cut here ]----- 
> > section, making it more likely that users (and tools like kerneloops) 
> > pick up the message in addition to just the bare WARNING.
> > 
> > The first few patches have been in -mm for a long time; the later ones 
> > are newer and introduce more users of WARN().
> 
> i've created a new -git based topic branch in tip/core/warn-API and 
> picked up your patches:

um, why?

If you merge this into linux-next then it will trash already-merged patches
in -mm and, more particularly, it will trash other trees which you aren't
looking at, causing Stephen problems.

The way to merge this code is to get the base patches into mainline and
then trickle the dependent patches into subsystem trees, or direct into
mainline after the subsystem trees have merged, and with suitable acks.

You aren't set up to do that?
--
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/