From: Gregory Price <gregory.price@memverge.com>
To: Andrei Vagin <avagin@gmail.com>
Cc: Oleg Nesterov <oleg@redhat.com>,
Gregory Price <gourry.memverge@gmail.com>,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-doc@vger.kernel.org, linux-kselftest@vger.kernel.org,
krisman@collabora.com, tglx@linutronix.de, luto@kernel.org,
peterz@infradead.org, ebiederm@xmission.com,
akpm@linux-foundation.org, adobriyan@gmail.com, corbet@lwn.net,
shuah@kernel.org
Subject: Re: [PATCH 3/3] ptrace,syscall_user_dispatch: add a getter/setter for sud configuration
Date: Tue, 24 Jan 2023 16:39:12 -0500 [thread overview]
Message-ID: <Y9BQAEVp/oGjZz46@memverge.com> (raw)
In-Reply-To: <CANaxB-wASWa1k6X5umJ=wt-K47uiBo9N5hxc--xz5cmU2bvysA@mail.gmail.com>
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.
next prev parent reply other threads:[~2023-01-24 21:39 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-23 3:29 [PATCH v5 0/3] Checkpoint Support for Syscall User Dispatch Gregory Price
2023-01-23 3:29 ` [PATCH v5 1/3] ptrace,syscall_user_dispatch: Implement Syscall User Dispatch Suspension Gregory Price
2023-01-23 3:29 ` [PATCH 2/3] fs/proc/array: Add Syscall User Dispatch to proc status Gregory Price
2023-01-23 3:29 ` [PATCH 3/3] ptrace,syscall_user_dispatch: add a getter/setter for sud configuration Gregory Price
2023-01-23 15:41 ` Oleg Nesterov
2023-01-23 18:12 ` Gregory Price
2023-01-23 19:52 ` Oleg Nesterov
2023-01-24 15:59 ` Gregory Price
2023-01-24 16:43 ` Oleg Nesterov
2023-01-24 16:54 ` Gregory Price
2023-01-24 17:58 ` Andrei Vagin
2023-01-24 21:39 ` Gregory Price [this message]
2023-01-24 2:51 ` Andrei Vagin
2023-01-24 3:30 ` Gregory Price
-- strict thread matches above, loose matches on Subject: below --
2023-01-18 20:10 [PATCH v2 0/3] Checkpoint Support for Syscall User Dispatch Gregory Price
2023-01-18 20:10 ` [PATCH 3/3] ptrace,syscall_user_dispatch: add a getter/setter for sud configuration Gregory Price
2023-01-18 23:43 ` kernel test robot
2023-01-19 1:06 ` kernel test robot
2023-01-19 1:16 ` kernel test robot
2023-01-19 2:39 ` kernel test robot
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=Y9BQAEVp/oGjZz46@memverge.com \
--to=gregory.price@memverge.com \
--cc=adobriyan@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=avagin@gmail.com \
--cc=corbet@lwn.net \
--cc=ebiederm@xmission.com \
--cc=gourry.memverge@gmail.com \
--cc=krisman@collabora.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=luto@kernel.org \
--cc=oleg@redhat.com \
--cc=peterz@infradead.org \
--cc=shuah@kernel.org \
--cc=tglx@linutronix.de \
/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