linux-kernel - Re: [PATCH] proc: constify status array

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: <AANLkTim8S_hjGj3m7FF+1gKOk0Rp1g350NdA1L8kiqzg@mail.gmail.com>
Date:	Wed, 30 Mar 2011 12:56:18 +0300
From:	Alexey Dobriyan <adobriyan@...il.com>
To:	Mike Frysinger <vapier@...too.org>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] proc: constify status array

On Wed, Mar 30, 2011 at 9:09 AM, Mike Frysinger <vapier@...too.org> wrote:
> -static const char *task_state_array[] = {
> +static const char * const task_state_array[] = {

Why this is needed for task_state_array, but not for, say, tgid_base_stuff?

00000000000000e0 d task_state_array
0000000000000a50 r tgid_base_stuff

This double const is ugly.
--
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/