linux-kernel - Re: [PATCH] "volatile considered harmful", take 3

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: <464542B1.3040403@garzik.org>
Date:	Sat, 12 May 2007 00:29:37 -0400
From:	Jeff Garzik <jeff@...zik.org>
To:	Satyam Sharma <satyam.sharma@...il.com>
CC:	Jonathan Corbet <corbet@....net>, akpm@...ux-foundation.org,
	linux-kernel@...r.kernel.org, Johannes Stezenbach <js@...uxtv.org>,
	Jesper Juhl <jesper.juhl@...il.com>,
	Randy Dunlap <randy.dunlap@...cle.com>,
	Heikki Orsila <shdl@...alwe.fi>,
	"H. Peter Anvin" <hpa@...or.com>,
	jimmy bahuleyan <knight.camelot@...il.com>,
	Stefan Richter <stefanr@...6.in-berlin.de>
Subject: Re: [PATCH] "volatile considered harmful", take 3

Satyam Sharma wrote:
> On 5/11/07, Jonathan Corbet <corbet@....net> wrote:
>> +  - Pointers to data structures in coherent memory which might be 
>> modified
>> +    by I/O devices can, sometimes, legitimately be volatile.  A ring 
>> buffer
>> +    used by a network adapter, where that adapter changes pointers to
>> +    indicate which descriptors have been processed, is an example of 
>> this
>> +    type of situation.
> 
> is a legitimate use case for volatile is still not clear to me (I

IMO it is not.  We do /not/ want to encourage volatile use in those 
cases, and indeed, it's not necessary even if you can rationalize the 
use of the English word "volatile" to describe the situation.

Drivers work quite well without volatile in such situations.

	Jeff


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