[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <874kq2o7zy.fsf@nanos.tec.linutronix.de>
Date: Mon, 20 Jul 2020 11:23:13 +0200
From: Thomas Gleixner <tglx@...utronix.de>
To: Andy Lutomirski <luto@...nel.org>,
Gabriel Krisman Bertazi <krisman@...labora.com>
Cc: LKML <linux-kernel@...r.kernel.org>, kernel@...labora.com,
Matthew Wilcox <willy@...radead.org>,
Andrew Lutomirski <luto@...nel.org>,
Paul Gofman <gofmanp@...il.com>,
Kees Cook <keescook@...omium.org>,
"open list\:KERNEL SELFTEST FRAMEWORK"
<linux-kselftest@...r.kernel.org>, Shuah Khan <shuah@...nel.org>
Subject: Re: [PATCH v4 1/2] kernel: Implement selective syscall userspace redirection
Andy Lutomirski <luto@...nel.org> writes:
> On Thu, Jul 16, 2020 at 12:31 PM Gabriel Krisman Bertazi
> <krisman@...labora.com> wrote:
> The amount of syscall entry wiring that arches need to do is IMO
> already a bit out of hand. Should we instead rename TIF_SECCOMP to
> TIF_SYSCALL_INTERCEPTION and have one generic callback that handles
> seccomp and this new thing?
The right way to go is to consolidate all the stupidly different
entry/exit work handling implementations and have exactly one in generic
code, i.e. what I posted a few days ago.
Then we can make new features only available in the generic version by
hiding the new functionality in the core code and not exposing the
functions to architecture implementations.
Making it easy for architectures to keep their own variant forever just
proliferates the mess we have right now.
Thanks,
tglx
Powered by blists - more mailing lists