linux-kernel - Re: [Bugme-new] [Bug 7724] New: asm/types.h should define _

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-next>] [day] [month] [year] [list]

Message-Id: <20061221.125850.125884789.davem@davemloft.net>
Date:	Thu, 21 Dec 2006 12:58:50 -0800 (PST)
From:	David Miller <davem@...emloft.net>
To:	akpm@...l.org
Cc:	netdev@...r.kernel.org, bugme-daemon@...zilla.kernel.org,
	uberlord@...too.org, linux-kernel@...r.kernel.org
Subject: Re: [Bugme-new] [Bug 7724] New: asm/types.h should define __u64 if
 isoc99

From: Andrew Morton <akpm@...l.org>
Date: Thu, 21 Dec 2006 12:49:54 -0800

> >            Summary: asm/types.h should define __u64 if isoc99

Platform specific bug, and has nothing to do with networking.

This problem will occur with any user visible interface definition
that uses __u64, and there are several both in and outside the
networking.

x86 and perhaps others protect the __u64 definition with:

	defined(__GNUC__) && !defined(__STRICT_ANSI__)

for whatever reason, probably to avoid "long long" or something like
that.  But even that theory makes no sense.

I do not make this protection on any of the sparc ports, even 32-bit
sparc, for example, so I find it really strange that x86 does this.
-
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/