linux-kernel - Re: [PATCH 1/5] proc: Make the generation of the self symlink table driven.

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: <Pine.LNX.4.61.0609081851260.19699@yvahk01.tjqt.qr>
Date:	Fri, 8 Sep 2006 18:55:10 +0200 (MEST)
From:	Jan Engelhardt <jengelh@...ux01.gwdg.de>
To:	"Eric W. Biederman" <ebiederm@...ssion.com>
cc:	Andrew Morton <akpm@...l.org>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/5] proc: Make the generation of the self symlink table
 driven.

>Regardless this isn't a case where the C precedence is wrong.
>"a < b | 1" is an example of C getting the precedence wrong.

Blame the creator of C.
But maybe this was intended, since | is a logical operation, as is <, 
while + is an arithmetic one. Programmatically probably not making much 
sense, bitfield |= a < b is one use case.

>Having to remember where C is wrong and in what circumstances is
>harder than just putting in parenthesis.

The GNU C compiler will warn you where such may happen, but
currently does so - too bad - only with && and ||.
 c.c:2: warning: suggest parentheses around && within ||

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