linux-kernel - Re: [PATCH] trace_syscalls: cleanup for syscalls

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: <1262797070.28171.2972.camel@gandalf.stny.rr.com>
Date:	Wed, 06 Jan 2010 11:57:50 -0500
From:	Steven Rostedt <rostedt@...dmis.org>
To:	Lai Jiangshan <laijs@...fujitsu.com>
Cc:	Frederic Weisbecker <fweisbec@...il.com>,
	Ingo Molnar <mingo@...e.hu>,
	LKML <linux-kernel@...r.kernel.org>,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [PATCH] trace_syscalls: cleanup for syscalls_metadata

On Wed, 2010-01-06 at 20:39 +0800, Lai Jiangshan wrote:
> NR_syscalls is compile-time constant.

The question is, is that always true on all archs, and will that always
be true?

Unless we can guarantee somewhere that NR_syscalls must be constant on
all archs, we can't make this change. If it is guaranteed, then sure,
this patch is fine.

> so we allocates memory for syscalls_metadata at compile-time.
> 
> Signed-off-by: Lai Jiangshan <laijs@...fujitsu.com>

-- Steve


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