linux-kernel - Re: [RFC][3/11][MANUX] Kernel compatibility : syscall numbers

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]

Date:	Wed, 16 Apr 2014 09:03:39 +0200
From:	Clemens Ladisch <clemens@...isch.de>
To:	Emmanuel Colbus <ecolbus@...ux.info>, linux-kernel@...r.kernel.org
Subject: Re: [RFC][3/11][MANUX] Kernel compatibility : syscall numbers

Emmanuel Colbus wrote:
> I have a question regarding vector 0x80.
>
> As I mentionned earlier, my OS's internals are very different from
> Linux's, thus I have had a need for a few new syscalls. Since I wanted
> to avoid any collision with Linux

... you could just use another vector, such as 0x81.

> but I also wanted to keep the ability to put the syscall table in
> a single 4096-byte page on 64-bit computers (on which I hope to run
> one day), I chose to start taking syscall number 511, and to progress
> downwards - currently, I'm using numbers 511 through 501 included

These implementation details do not need to show up in the interface:

int syscall_0x81(int nr, ...)
{
    if (nr in range)
        return table[511 - nr](...);
}


Regards,
Clemens
--
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/