linux-kernel - Re: [PATCH] device: add dev_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] [day] [month] [year] [list]

Message-Id: <7DD6AD65-0F6E-402E-BE8D-05E03E56E03E@ti.com>
Date:	Wed, 16 Mar 2011 17:53:53 +0200
From:	Felipe Balbi <balbi@...com>
To:	Greg KH <gregkh@...e.de>
Cc:	Felipe Balbi <balbi@...com>,
	Grant Likely <grant.likely@...retlab.ca>,
	Magnus Damm <damm@...nsource.se>,
	"Eric W. Biederman" <ebiederm@...ssion.com>,
	Andi Kleen <ak@...ux.intel.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] device: add dev_WARN_ONCE


On Mar 16, 2011, at 4:39 PM, Greg KH wrote:

> On Wed, Mar 16, 2011 at 03:59:35PM +0200, Felipe Balbi wrote:
>> it's quite useful to print the device name
>> on the stack dump caused by WARN(), but
>> there are other cases where we might want
>> to use WARN_ONCE.
>> 
>> Introduce a helper similar to dev_WARN() for
>> that case too.
>> 
>> Signed-off-by: Felipe Balbi <balbi@...com>
> 
> Do you have code that needs this for .39, or can it wait for .40?

it can definitely wait :-)

-- 
balbi

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