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: <20080106092619.GA23627@elte.hu>
Date:	Sun, 6 Jan 2008 10:26:19 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Arjan van de Ven <arjan@...radead.org>
Cc:	linux-kernel@...r.kernel.org, akpm@...ux-foundation.org,
	heiko.carstens@...ibm.com, olof@...om.net, mpm@...enic.com
Subject: Re: [patch 0/5] enhance WARN_ON series


* Arjan van de Ven <arjan@...radead.org> wrote:

> 3rd try for this patch series; now with a split up patch for __WARN_ON
> 
> This series has the goal of extending the usefulness of the WARN_ON() 
> information, at least on architectures that use the generic WARN_ON() 
> infrastructure. (Those who do their own thing either already have the 
> extra information, or could consider switching to the generic code). 
> In order to do that, WARN_ON() first needs to be uninlined since 
> there's like 1200 callsites and adding code to each of those isn't 
> pretty.
> 
> As part of this, I had to split the __WARN_ON patch in -mm into 2 
> pieces, one to introduce __WARN_ON, and a separate one to do the ifdef 
> cleanup.

i've added the first 3 patches to x86.git, for further testing - and 
would expect -mm to pick up #4/#5.

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