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]
Date:	Mon, 10 Mar 2014 19:33:03 -0700
From:	"H. Peter Anvin" <hpa@...or.com>
To:	David Miller <davem@...emloft.net>, torvalds@...ux-foundation.org
CC:	ast@...mgrid.com, dborkman@...hat.com, mingo@...nel.org,
	wad@...omium.org, rostedt@...dmis.org, a.p.zijlstra@...llo.nl,
	hagen@...u.net, jesse@...ira.com, tglx@...utronix.de,
	edumazet@...gle.com, akpm@...ux-foundation.org, fweisbec@...il.com,
	acme@...radead.org, penberg@....fi, arjan@...radead.org,
	hch@...radead.org, xemul@...allels.com,
	linux-kernel@...r.kernel.org, netdev@...r.kernel.org
Subject: Re: [PATCH v8 net-next 1/3] filter: add Extended BPF interpreter and converter

Why not for variables? It makes a lot of sense of nothing else to avoid the confusion that invariably happens when someone decides to introduce the value 2 or -1 to an existing variable (and yes, thus has happened a number of times.)

Not to mention they take a single byte rather than four for an int if stored in memory.

On March 10, 2014 7:24:49 PM PDT, David Miller <davem@...emloft.net> wrote:
>From: Linus Torvalds <torvalds@...ux-foundation.org>
>Date: Mon, 10 Mar 2014 19:02:18 -0700
>
>> I would generally suggest that people only use "bool" for function
>> return types, and absolutely nothing else. Seriously.
>
>I think it makes sense for function arguments too.

-- 
Sent from my mobile phone.  Please pardon brevity and lack of formatting.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Powered by blists - more mailing lists