linux-kernel - Re: [PATCH -mm] Introduce U16_MAX and U32

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: <20070731115729.64c875d4.akpm@linux-foundation.org>
Date:	Tue, 31 Jul 2007 11:57:29 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Satyam Sharma <satyam@...radead.org>
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH -mm] Introduce U16_MAX and U32_MAX

On Tue, 31 Jul 2007 21:56:12 +0530 (IST)
Satyam Sharma <satyam@...radead.org> wrote:

> --- a/include/linux/kernel.h
> +++ b/include/linux/kernel.h
> @@ -30,6 +30,9 @@ extern const char linux_proc_banner[];
>  #define LLONG_MIN	(-LLONG_MAX - 1)
>  #define ULLONG_MAX	(~0ULL)
>  
> +#define U16_MAX		((u16) ~0U)
> +#define U32_MAX		((u32) ~0U)
> +

hm, I'd have thought that there's a risk of gcc warnings here, forcing
0xffffffff into a u16, but apparently not.

Still, I think it'd be tidier here to tell the truth and use plain
old 0xffff and 0xffffffff?
-
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/