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] [day] [month] [year] [list]

Message-ID: <534E5A10.9040706@manux.info>
Date:	Wed, 16 Apr 2014 12:23:12 +0200
From:	Emmanuel Colbus <ecolbus@...ux.info>
To:	Clemens Ladisch <clemens@...isch.de>
CC:	linux-kernel@...r.kernel.org
Subject: Re: [RFC][3/11][MANUX] Kernel compatibility : syscall numbers

Le 16/04/2014 09:03, Clemens Ladisch a écrit :
> 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
> 

This would stop working as soon as I implemented any syscall/sysret or
sysenter/sysexit-like thing, as this technique has no notion of a
syscall vector.

Regards,

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