linux-kernel - Re: -mm merge plans for 2.6.23 -- sys

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 10 Jul 2007 20:05:31 +0200
From:	Heiko Carstens <heiko.carstens@...ibm.com>
To:	Theodore Tso <tytso@....edu>,
	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org, Andi Kleen <ak@...e.de>,
	Amit Arora <aarora@...ibm.com>,
	Martin Schwidefsky <schwidefsky@...ibm.com>
Subject: Re: -mm merge plans for 2.6.23 -- sys_fallocate

> Alternatively I can push them directly to Linus along with other ext4
> patches.  We can drop the s390 patch if Martin or Heiko wants to wire
> it up themselves.

Yes, please drop the s390 patch. In general it seems to be better if only
one architecture gets a syscall wired up initially and let other arches
follow later.

Just wondering if the x86_64 compat syscall gets ever fixed? I think
I mentioned already three or four times to Amit that it is broken.
Or is it that nobody cares? Dunno..

In addition there used to be a somewhat inofficial rule that new syscalls
have to come with a test program, so people can easily test if they wired
up the syscall correctly.
-
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/