linux-kernel - Re: [GIT PULL] ext4 changes for 3.15

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: <7cc6f198-832f-4af7-82ea-2b89ad737885@email.android.com>
Date:	Wed, 09 Apr 2014 12:19:52 -0700
From:	"H. Peter Anvin" <hpa@...or.com>
To:	"Theodore Ts'o" <tytso@....edu>,
	Geert Uytterhoeven <geert@...ux-m68k.org>
CC:	Arnd Bergmann <arnd@...db.de>, Sam Ravnborg <sam@...nborg.org>,
	linux-kbuild <linux-kbuild@...r.kernel.org>,
	Miklos Szeredi <miklos@...redi.hu>, Jan Kara <jack@...e.cz>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	"linux-ext4@...r.kernel.org" <linux-ext4@...r.kernel.org>,
	Al Viro <viro@...iv.linux.org.uk>,
	"Michael Kerrisk (man-pages)" <mtk.manpages@...il.com>
Subject: Re: [GIT PULL] ext4 changes for 3.15

It is quite frankly ridiculous how much work it takes to wire up a new system call.  It should be possible to do it across architectures without all this crap.

On April 9, 2014 11:23:24 AM PDT, Theodore Ts'o <tytso@....edu> wrote:
>On Wed, Apr 09, 2014 at 07:48:32PM +0200, Geert Uytterhoeven wrote:
>> >
>> > I'm missing context here, but as an x86 maintainer I have no
>intention
>> > of allowing system calls that aren't x86-specific to be added to
>x86-64
>> > only.
>> 
>> commit 520c8b16505236fc82daa352e6c5e73cd9870cff
>> Author: Miklos Szeredi <mszeredi@...e.cz>
>> Date:   Tue Apr 1 17:08:42 2014 +0200
>> 
>>     vfs: add renameat2 syscall
>> 
>> It was added to arch/x86/syscalls/syscall_64.tbl only.
>
>To be fair, part of the problem is that we don't have good
>documentation about best practices in what people should do if adding
>new system calls.  (i.e., creating a man page and pulling in Michael
>Kerrisk, adding tests, wiring up both x86_64 and i386, sending mail to
>linux-arch, the scripts/checksyscalls.sh script, etc.)
>
>I'll confess to being ignorant about the checksyscalls.sh script, and
>while I had known about the existence of the linux-arch list, I had
>forgotten about it, so if I had tried to add a new system call, it's
>likely I would have missed at one or more of these steps.
>
>       	       	    	      	     - Ted
>
>
>
>
>> 
>> Gr{oetje,eeting}s,
>> 
>>                         Geert
>> 
>> --
>> Geert Uytterhoeven -- There's lots of Linux beyond ia32 --
>geert@...ux-m68k.org
>> 
>> In personal conversations with technical people, I call myself a
>hacker. But
>> when I'm talking to journalists I just say "programmer" or something
>like that.
>>                                 -- Linus Torvalds

-- 
Sent from my mobile phone.  Please pardon brevity and lack of formatting.
--
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/