linux-kernel - Re: [PATCH] introduce kernel_execve function to replace __KERNEL_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: <200608201333.02951.chase.venters@clientec.com>
Date:	Sun, 20 Aug 2006 13:32:39 -0500
From:	Chase Venters <chase.venters@...entec.com>
To:	Andrew Morton <akpm@...l.org>
Cc:	Arnd Bergmann <arnd@...db.de>,
	Björn Steinbrink <B.Steinbrink@....de>,
	Russell King <rmk+lkml@....linux.org.uk>,
	rusty@...tcorp.com.au, linux-kernel@...r.kernel.org,
	linux-arch@...r.kernel.org
Subject: Re: [PATCH] introduce kernel_execve function to replace __KERNEL_SYSCALLS__

On Sunday 20 August 2006 13:25, Andrew Morton wrote:
> On Sun, 20 Aug 2006 12:36:49 -0500
>
> Chase Venters <chase.venters@...entec.com> wrote:
> > Unless 'errno' has some significant reason to live on in the kernel, I
> > think it would be better to kill it and write kernel syscall macros that
> > don't muck with it.
>
> We have been working in that direction.  It's certainly something we'd like
> to kill off.

Perhaps Arnd's patch is a good step in that direction then. A secondary 
suggestion is to put a big comment there that explains "Yes, we know this is 
ugly, it's going to die soon."

I'd also consider going so far as just returning -1 if we failed, since we 
can't quite trust errno anyway.

Thanks,
Chase
-
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/