linux-kernel - Re: [PATCH] Introducing asm/syscalls.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: <1216580711.2475.175.camel@shinybook.infradead.org>
Date:	Sun, 20 Jul 2008 12:05:11 -0700
From:	David Woodhouse <dwmw2@...radead.org>
To:	Jaswinder Singh <jaswinder@...radead.org>
Cc:	LKML <linux-kernel@...r.kernel.org>, Ingo Molnar <mingo@...e.hu>,
	rth@...ddle.net, rmk@....linux.org.uk, hskinnemoen@...el.com,
	cooloney@...nel.org, starvik@...s.com, dhowells@...hat.com,
	ysato@...rs.sourceforge.jp, tony.luck@...el.com,
	takata@...ux-m32r.org, geert@...ux-m68k.org, ralf@...ux-mips.org,
	matthew@....cx, schwidefsky@...ibm.com, lethal@...ux-sh.org,
	chris@...kel.net
Subject: Re: [PATCH] Introducing asm/syscalls.h

On Sun, 2008-07-20 at 14:39 +0530, Jaswinder Singh wrote:
> 
> Declaring arch-dependent syscalls for all architectures
> Beneficial for kernel and userspace

Not really beneficial for userspace at all. Don't expose it.

I'm a little dubious about touching all architectures at once.

It might be nicer to do a first patch which adds an _empty_
<asm/syscalls.h> on each platform, and includes that from
<linux/syscalls.h>. And then follow up with one patch per architecture.

Have you compile-tested them all?

-- 
dwmw2

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