linux-kernel - Re: why is asm-parisc/ioctl.h subtly different from asm-generic/ioctl.h?

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: <20070224184516.GA6755@athena.road.mcmartin.ca>
Date:	Sat, 24 Feb 2007 13:45:16 -0500
From:	Kyle McMartin <kyle@...artin.ca>
To:	"Robert P. J. Day" <rpjday@...dspring.com>
Cc:	Linux kernel mailing list <linux-kernel@...r.kernel.org>
Subject: Re: why is asm-parisc/ioctl.h subtly different from asm-generic/ioctl.h?

On Sat, Feb 24, 2007 at 05:34:15AM -0500, Robert P. J. Day wrote:
> 
>   just noticed that parisc's ioctl.h file, rather than simply
> including asm-generic/ioctl.h, has its own copy whose sole
> (meaningful) difference from the generic one is:
> 
> $ diff include/{asm-generic,asm-parisc}/ioctl.h
> ...
> 41,42c54,55
> < #define _IOC_WRITE    1U
> < #define _IOC_READ     2U
> ---
> > #define _IOC_WRITE    2U
> > #define _IOC_READ     1U
> 
>  so parisc is identical except that it switches the meaning of the
> direction field?  is there a reason for this?  just curious.
> 

HP-UX compatibility.

#define IOC_OUT 0x40000000
#define IOC_IN (int)0x80000000

PS: It would be wise to ask questions on the pertinent mailing lists...

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