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: <20140407140745.GA8855@thunk.org>
Date:	Mon, 7 Apr 2014 10:07:45 -0400
From:	Theodore Ts'o <tytso@....edu>
To:	Miklos Szeredi <miklos@...redi.hu>
Cc:	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>
Subject: Re: [GIT PULL] ext4 changes for 3.15

On Mon, Apr 07, 2014 at 03:15:36PM +0200, Miklos Szeredi wrote:
> >
> > Is there anything obvious that I might be doing wrong?
> 
> I only wired up the syscall for x86_64.   Who's responsible for adding
> all the syscall tables for the various architectures?

Ah, and I was testing with i386, not x86_64, so that it explains that.

It's been quite a while since I've worked to add a new system call,
but my impressure is that in general the person who creates the new
system call needs to reach out to the architecture maintainers
(preferably with a patch :-), since otherwise the architecture
maintainers would have no idea that a new syscall has been added.

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