linux-kernel - Re: [x86 setup 17/33] A20 handling code

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: <4693D10D.8010502@zytor.com>
Date:	Tue, 10 Jul 2007 11:33:49 -0700
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Jan Engelhardt <jengelh@...putergmbh.de>
CC:	linux-kernel@...r.kernel.org, linux-arch@...r.kernel.org,
	andi@...stfloor.org, akpm@...ux-foundation.org
Subject: Re: [x86 setup 17/33] A20 handling code

Jan Engelhardt wrote:
> On Jul 9 2007 19:51, H. Peter Anvin wrote:
> 
>> +		status = inb(0x64);
>> +		if (status & 1) {
>> +			/* Read and discard input data */
>> +			io_delay();
>> +			(void)inb(0x60);
> 
> Is the (void) cast needed for some obscure reason? Let's hope inb _is_ declared
> as volatile. (Minus the volatile flames.
> 

The (void) cast is there as a stylistic device, it tells the human
reader "yes, I really meant to read this value and throw it away."

	-hpa

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