Re: [PATCH v13 0/3] Add kernel seccomp support for m68k

[Michael Schmitz <schmitzmic@gmail.com>]

Hi Adrian,

Am 16.01.2023 um 22:12 schrieb John Paul Adrian Glaubitz:
> Hi Michael!
>
> On 1/14/23 01:00, Michael Schmitz wrote:
>>> Unfortunately, libseccomp fails to build after I updated the
>>> syscalls.csv file
>>> after adding m68k support. It seems that the problem are a number of
>>> syscalls
>>> that exist on m68k only:
>>>
>>>   CC       libseccomp_la-syscalls.perf.lo
>>> syscalls.perf:152:70: error: '__PNR_getpagesize' undeclared here (not in
>>> a function)
>>>   152 |
>>> getpagesize,119,__PNR_getpagesize,SCMP_KV_UNDEF,__PNR_getpagesize,SCMP_KV_UNDEF,__PNR_getpagesize,SCMP_KV_UNDEF,__PNR_getpagesize,SCMP_KV_UNDEF,__PNR_getpagesize,SCMP_KV_UNDEF,166,SCMP_KV_UNDEF,__PNR_getpagesize,SCMP_KV_UNDEF,__PNR_getpagesize,SCMP_KV_UNDEF,__PNR_getpagesize,SCMP_KV_UNDEF,__PNR_getpagesize,SCMP_KV_UNDEF,__PNR_getpagesize,SCMP_KV_UNDEF,__PNR_getpagesize,SCMP_KV_UNDEF,__PNR_getpagesize,SCMP_KV_UNDEF,__PNR_getpagesize,SCMP_KV_UNDEF,__PNR_getpagesize,SCMP_KV_UNDEF,__PNR_getpagesize,SCMP_KV_UNDEF,__PNR_getpagesize,SCMP_KV_UNDEF
>>>
>>
>> That one also exists on alpha and sparc. The other two are indeed
>> unique to m68k.
>>
>> There must have been other cases of novel syscalls added to libseccomp
>> before?
>
> Neither alpha nor sparc are supported by libseccomp, so I think that's
> not an argument.

Explains why getpagesize still is not handled by libseccomp, then.

Now do any of the other architectures recently added to libseccomp have 
non-standard syscalls? (Trying to work out what commits might hold the 
secret to adding support for new syscalls...)

Cheers,

	Michael

>
> Adrian
>