linux-kernel - Re: (Short?) merge window reminder

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: <20110525122618.GA14303@colin.search.kasperd.net>
Date:	Wed, 25 May 2011 14:26:18 +0200
From:	Kasper Dupont <kasperd@...xn.25.may.2011.kasperd.net>
To:	Valdis.Kletnieks@...edu
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: (Short?) merge window reminder

On 24/05/11 21.13, Valdis.Kletnieks@...edu wrote:
> Well, if we're looking at ELF-sized ABI changes, how about 3.0 be the
> release where we re-sync the syscall numbers on all the archs? ;)

If you want to do that I think the best way to do it is to
have both the old and the new numbers co-exist through the
3.x series and the old ones go away in 4.0.

You'd first have to find the highest number currently
assigned and then add a bit of safety margin to decide on
a starting point for the new numbers.

Should architecture dependent system calls be assigned
from a separate interval where they could overlap between
architectures? Or should they be assigned from the same
sequence as other calls and return -ENOSYS on other
architectures than the one they were targeted for?

Or was it all a joke, and you don't actually want that
cleanup to happen because of too much breakage?

-- 
Kasper Dupont -- Rigtige mænd skriver deres egne backupprogrammer
#define _(_)"d.%.4s%."_"2s" /* This is my email address */
char*_="@2kaspner"_()"%03"_("4s%.")"t\n";printf(_+11,_+6,_,11,_+2,_+7,_+6);
--
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/