From: Ralf Baechle <ralf@linux-mips.org>
To: Cyrill Gorcunov <gorcunov@openvz.org>,
Andrew Morton <akpm@linux-foundation.org>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Kees Cook <keescook@chromium.org>,
linux-kernel@vger.kernel.org,
Linux-Arch <linux-arch@vger.kernel.org>,
Heiko Carstens <heiko.carstens@de.ibm.com>
Subject: Re: sys_kcmp (was: Re: [PATCH 1/2] ARM: add finit_module syscall to ARM)
Date: Sat, 22 Sep 2012 15:38:47 +0200 [thread overview]
Message-ID: <20120922133847.GC20003@linux-mips.org> (raw)
In-Reply-To: <20120922132046.GA4260@flint.arm.linux.org.uk>
On Sat, Sep 22, 2012 at 02:20:46PM +0100, Russell King wrote:
> 2. There allegedly exists a patch to remove x86isms from sys_kcmp -
> allegedly also in akpm's tree. However, I've looked through the code in
> mainline, and nothing stands out. Ralf Beachle also said yesterday that
> he has looked through from the MIPS PoV and also can't see any x86isms,
> so we're both thinking that it should merely have the x86 dependency
> removed.
>
> 3. Until the x86 dependency is gone (that depends on what akpm proposes to
> do with the patches he's allegedly sitting on), non-x86 arches can only
> reserve the syscall, and add an IGNORE for it.
There is a weak definition provided in kernel/sys_ni.c so it actually can
be properly wired up in preparation for the day when the dependency in
Kconfig gets fixed.
> It would be good to at least get checksyscalls.sh fixed so arch maintainers
> get their warnings for new syscalls back.
Indeed. That script has become just too important.
Ralf
next prev parent reply other threads:[~2012-09-22 13:39 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-22 10:56 sys_kcmp (was: Re: [PATCH 1/2] ARM: add finit_module syscall to ARM) Geert Uytterhoeven
2012-09-22 11:45 ` Cyrill Gorcunov
2012-09-22 13:20 ` Russell King
2012-09-22 13:38 ` Ralf Baechle [this message]
2012-09-22 15:37 ` Cyrill Gorcunov
2012-09-22 18:47 ` Andrew Morton
2012-09-24 16:21 ` Mark Salter
2012-09-24 16:49 ` Cyrill Gorcunov
2012-09-24 17:42 ` Cyrill Gorcunov
2012-09-24 18:16 ` Mark Salter
2012-09-24 18:55 ` Cyrill Gorcunov
2012-09-24 18:29 ` sys_kcmp Eric W. Biederman
2012-09-24 18:51 ` sys_kcmp Cyrill Gorcunov
2012-09-24 20:35 ` sys_kcmp Cyrill Gorcunov
2012-09-24 20:44 ` sys_kcmp Eric W. Biederman
2012-09-24 20:53 ` sys_kcmp Cyrill Gorcunov
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=20120922133847.GC20003@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=akpm@linux-foundation.org \
--cc=geert@linux-m68k.org \
--cc=gorcunov@openvz.org \
--cc=heiko.carstens@de.ibm.com \
--cc=keescook@chromium.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.