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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87r6cecmde.fsf@saeurebad.de>
Date:	Wed, 07 May 2008 14:46:53 +0200
From:	Johannes Weiner <hannes@...urebad.de>
To:	Arjan van de Ven <arjan@...radead.org>
Cc:	linux-kernel@...r.kernel.org, akpm@...ux-foundation.org
Subject: Re: [patch 1/3] Rename WARN() to WARNING() to clear the namespace

Hi Arjan,

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

> Subject: Rename WARN() to WARNING() to clear the namespace
> From: Arjan van de Ven <arjan@...ux.intel.com>
>
> We want to use WARN() as a variant of WARN_ON(), however
> a few drivers are using WARN() internally. This patch renames
> these to WARNING() to avoid the namespace clash.
> A few cases were defining but not using the thing, for those
> cases I just deleted the definition.

It always bugged me that there is no WARN() that behaves similar to
BUG().

What do you think of making WARN() just emit the warning
unconditionally?

And maybe add the possibility to emit a text as well on both WARN() and
BUG()?  BUG("my kitten was hit by page %p!\n", page);

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