linux-kernel - Re: [PATCH v2 3/4] m68k: Wire up direct ipc calls

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

Message-ID: <CAMuHMdW+An7Qa5Jt=JpHooy4Q9LopdKJWrpcJ0-0YsFi-i_FUQ@mail.gmail.com>
Date:	Thu, 17 Sep 2015 17:18:53 +0200
From:	Geert Uytterhoeven <geert@...ux-m68k.org>
To:	Andreas Schwab <schwab@...ux-m68k.org>
Cc:	Greg Ungerer <gerg@...inux.org>,
	"Linux/m68k" <linux-m68k@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2 3/4] m68k: Wire up direct ipc calls

Hi Andreas,

On Thu, Sep 17, 2015 at 5:09 PM, Andreas Schwab <schwab@...ux-m68k.org> wrote:
> Geert Uytterhoeven <geert@...ux-m68k.org> writes:
>> You mean that we should drop "select ARCH_WANT_IPC_PARSE_VERSION",
>> but we can't do that because an indirect call through sys_ipc() would
>> still need it when dispatching to sys_{sem,shm,msg}ctl()?
>
> Yes.  But all architectures that currently use both sys_ipc and
> ARCH_WANT_IPC_PARSE_VERSION would benefit from decoupling it when they
> add the direct syscalls.

Do we currently have architectures that use both sys_ipc and the direct
syscalls, where keeping ipc_parse_version() in the direct syscalls is required?

Gr{oetje,eeting}s,

                        Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@...ux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds
--
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/