[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <Y9BQAEVp/oGjZz46@memverge.com>
Date: Tue, 24 Jan 2023 16:39:12 -0500
From: Gregory Price <gregory.price@...verge.com>
To: Andrei Vagin <avagin@...il.com>
Cc: Oleg Nesterov <oleg@...hat.com>,
Gregory Price <gourry.memverge@...il.com>,
linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org,
linux-doc@...r.kernel.org, linux-kselftest@...r.kernel.org,
krisman@...labora.com, tglx@...utronix.de, luto@...nel.org,
peterz@...radead.org, ebiederm@...ssion.com,
akpm@...ux-foundation.org, adobriyan@...il.com, corbet@....net,
shuah@...nel.org
Subject: Re: [PATCH 3/3] ptrace,syscall_user_dispatch: add a getter/setter
for sud configuration
On Tue, Jan 24, 2023 at 09:58:02AM -0800, Andrei Vagin wrote:
> >
> > *facepalm* good point, i'm wondering if there's a reason CRIU doesn't do
> > the same for SECCOMP.
>
> Because information about seccomp was in /proc/pid/status forever and we
> started using it before the ptrace interface was merged. I am not sure that
> this is the only reason, but it is definitely one of them.
>
Even better reason to drop it. I'll send out (hopefully) the final
configuration here shortly.
Glad this simplified down as much as it did.
Powered by blists - more mailing lists