Re: [PATCH 1/8] signal/alpha: Document a conflict with SI_USER for SIGTRAP

From	ebiederm@xmission.com (Eric W. Biederman)
Newsgroups	linux.kernel
Subject	Re: [PATCH 1/8] signal/alpha: Document a conflict with SI_USER for SIGTRAP
Date	2017-07-18 15:50 +0200
Message-ID	<u4B2W-32k-3@gated-at.bofh.it> (permalink)
References	<tY3x0-5xi-9@gated-at.bofh.it> <tY3x1-5xi-55@gated-at.bofh.it> <tYNTb-37u-9@gated-at.bofh.it> <u36DU-2z6-29@gated-at.bofh.it> <u49q1-2vC-15@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Show all headers | View raw

Michael Cree <mcree@orcon.net.nz> writes:

> On Fri, Jul 14, 2017 at 05:59:06AM -0500, Eric W. Biederman wrote:
>> in which cases the oddities will happen let alone test them.  Plus at
>> least for ia64 and alpha those architectures don't appear to be
>> receiving updates for new syscalls, and no new hardware is being built
>> so I don't know how much longer they will last.
>> 
>> That is building for alpha gives:
>> >   CALL    /home/eric/projects/linux/linux-exit-cleanups/scripts/checksyscalls.sh
>> > <stdin>:1239:2: warning: #warning syscall seccomp not implemented [-Wcpp]
>> > <stdin>:1248:2: warning: #warning syscall bpf not implemented [-Wcpp]
>> > <stdin>:1299:2: warning: #warning syscall userfaultfd not implemented [-Wcpp]
>> > <stdin>:1302:2: warning: #warning syscall membarrier not implemented [-Wcpp]
>> > <stdin>:1305:2: warning: #warning syscall mlock2 not implemented [-Wcpp]
>> > <stdin>:1308:2: warning: #warning syscall copy_file_range not implemented [-Wcpp]
>> > <stdin>:1311:2: warning: #warning syscall preadv2 not implemented [-Wcpp]
>> > <stdin>:1314:2: warning: #warning syscall pwritev2 not implemented [-Wcpp]
>> > <stdin>:1317:2: warning: #warning syscall pkey_mprotect not implemented [-Wcpp]
>> > <stdin>:1320:2: warning: #warning syscall pkey_alloc not implemented [-Wcpp]
>> > <stdin>:1323:2: warning: #warning syscall pkey_free not implemented [-Wcpp]
>> > <stdin>:1326:2: warning: #warning syscall statx not implemented [-Wcpp]
>
> Patches to wire up most of those syscalls on Alpha was posted recently
> along with others to fix module loading, etc., but unfortunately they
> do not appear to have been applied during the merge window...

Odd.

In general wiring up system calls is something that can even happen in
-rc2 or -rc3 as system calls get added in -rc1 and then the
architectures have a chance to send in the small patches wiring the up.
At least that is how I understand the usual rules for being a non-x86
architecture.

Eric

Back to linux.kernel | Previous | Next — Previous in thread | Find similar | Unroll thread

Thread

Re: [PATCH 1/8] signal/alpha: Document a conflict with SI_USER for SIGTRAP ebiederm@xmission.com (Eric W. Biederman) - 2017-07-14 13:10 +0200
  Re: [PATCH 1/8] signal/alpha: Document a conflict with SI_USER for  SIGTRAP Michael Cree <mcree@orcon.net.nz> - 2017-07-17 10:20 +0200
    Re: [PATCH 1/8] signal/alpha: Document a conflict with SI_USER for SIGTRAP ebiederm@xmission.com (Eric W. Biederman) - 2017-07-18 15:50 +0200

csiph-web