linux-kernel - Re: [PATCH 0/22] 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] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 21 Jul 2008 12:29:59 +0530
From:	Jaswinder Singh <jaswinder@...radead.org>
To:	Matthew Wilcox <matthew@....cx>
Cc:	Alexey Dobriyan <adobriyan@...il.com>,
	LKML <linux-kernel@...r.kernel.org>, Ingo Molnar <mingo@...e.hu>,
	kernelnewbies <kernelnewbies@...linux.org>,
	David Woodhouse <dwmw2@...radead.org>, 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, schwidefsky@...ibm.com, lethal@...ux-sh.org,
	chris@...kel.net
Subject: Re: [PATCH 0/22] Introducing asm/syscalls.h

Hello Matthew,

On Mon, 2008-07-21 at 00:16 -0600, Matthew Wilcox wrote:

> sys_fork() does seem to be the worst case scenario.  I suspect there's
> similar ones (clone?).  I still think it's worth adding them all to
> linux/syscalls.h.
> 

I tried my best to make things simpler. I also tried this in :- 
[PATCH 17/22] sh: Introducing asm/syscalls.h
[PATCH 21/22] x86: Introducing asm/syscalls.h

For same architecture it looks complex for 32 and 64 bit.

You can Imagine how linux/syscalls.h will look if we add all
architectures in it.

And you can imagine what will be size of linux/syscalls.h. As more than
60% of arch dependent syscalls have totally different prototypes.

Thank you,

Jaswinder Singh.




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