linux-kernel - Re: early exception error

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: <20090105154215.GI7645@localhost>
Date:	Mon, 5 Jan 2009 18:42:15 +0300
From:	Cyrill Gorcunov <gorcunov@...il.com>
To:	Jiri Slaby <jirislaby@...il.com>
Cc:	Andi Kleen <andi@...stfloor.org>,
	Johannes Weiner <hannes@...xchg.org>,
	Robert Hancock <hancockr@...w.ca>,
	linux-kernel@...r.kernel.org, david@...g.hm,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: early exception error

[Jiri Slaby - Mon, Jan 05, 2009 at 04:39:07PM +0100]
...
| > | I know, core devs are sane, but e.g. for reasons such as
| > | 
| > | {'a' is used here already}
| > | EARLY_BUG_ON(!(a = readl(...)))
| > | {use 'a' again}
| > | 
| > | to stay on the safe side.
| > 
| > I wouldn't populate this style Jiri. It become more complicated
| > as it should to be, agreed?
| 
| No, I tend to disagree. Macros should evaluate argument(s) the same no matter
| what is in .config.
| 

I see what you mean (now) -- and you're right!

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