From: Michael Cree <mcree@orcon.net.nz>
To: Chen Gang <xili_gchen_5257@hotmail.com>
Cc: rth@twiddle.net, ink@jurassic.park.msu.ru,
"mattst88@gmail.com" <mattst88@gmail.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-alpha@vger.kernel.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] alpha: Wire up missing syscalls
Date: Tue, 12 May 2015 20:59:52 +1200 [thread overview]
Message-ID: <20150512085952.GC5711@tower> (raw)
In-Reply-To: <BLU436-SMTP115284EEDC94CD99F399465B9DD0@phx.gbl>
On Sun, May 10, 2015 at 02:33:36AM +0800, Chen Gang wrote:
> The related warnings:
>
> CALL scripts/checksyscalls.sh
> <stdin>:1238:2: warning: #warning syscall seccomp not implemented [-Wcpp]
> <stdin>:1241:2: warning: #warning syscall getrandom not implemented [-Wcpp]
> <stdin>:1244:2: warning: #warning syscall memfd_create not implemented [-Wcpp]
> <stdin>:1247:2: warning: #warning syscall bpf not implemented [-Wcpp]
> <stdin>:1250:2: warning: #warning syscall execveat not implemented [-Wcpp]
Chen: Have you tested the syscalls you have wired up?
I have a suspicion that more is required to wire up the seccomp
syscall. At least some of the other older architectures had to
implement some extra arch dependent support to implement the seccomp
syscall. I don't know whether this is necessary or not on Alpha so
was wondering if this has been considered?
Matt: are you still feeding Alpha patches to Linus? I suspect there
might be a few other patches other than this one submitted to
linux-alpha that should be applied.
Cheers
Michael.
next prev parent reply other threads:[~2015-05-12 9:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-09 18:33 [PATCH] alpha: Wire up missing syscalls Chen Gang
2015-05-12 8:59 ` Michael Cree [this message]
2015-05-12 11:40 ` Chen Gang
2015-05-12 11:46 ` Chen Gang
2015-05-12 14:29 ` Dave Jones
2015-05-13 0:55 ` Chen Gang
2015-05-18 4:44 ` Chen Gang
2015-05-12 17:36 ` Matt Turner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150512085952.GC5711@tower \
--to=mcree@orcon.net.nz \
--cc=gregkh@linuxfoundation.org \
--cc=ink@jurassic.park.msu.ru \
--cc=linux-alpha@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mattst88@gmail.com \
--cc=rth@twiddle.net \
--cc=xili_gchen_5257@hotmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox