From: Pavel Tikhomirov <ptikhomirov@virtuozzo.com>
To: linux-kernel@vger.kernel.org
Cc: Eric Biederman <ebiederm@xmission.com>,
Kees Cook <keescook@chromium.org>,
Alexander Viro <viro@zeniv.linux.org.uk>,
Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Juri Lelli <juri.lelli@redhat.com>,
Vincent Guittot <vincent.guittot@linaro.org>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Steven Rostedt <rostedt@goodmis.org>,
Ben Segall <bsegall@google.com>, Mel Gorman <mgorman@suse.de>,
Daniel Bristot de Oliveira <bristot@redhat.com>,
Valentin Schneider <vschneid@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-ia64@vger.kernel.org, linux-mm@kvack.org,
linux-fsdevel@vger.kernel.org, kernel@openvz.org
Subject: Re: [PATCH 0/2] Introduce CABA helper process tree
Date: Fri, 10 Jun 2022 19:38:59 +0300 [thread overview]
Message-ID: <cb7f3533-a904-ef0f-e3a9-39eed6775aad@virtuozzo.com> (raw)
In-Reply-To: <20220610163214.49974-1-ptikhomirov@virtuozzo.com>
CC: kernel@openvz.org
On 10.06.2022 19:32, Pavel Tikhomirov wrote:
> Please see "Add CABA tree to task_struct" for deeper explanation, and
> "tests: Add CABA selftest" for a small test and an actual case for which
> we might need CABA.
>
> Probably the original problem of restoring process tree with complex
> sessions can be resolved by allowing sessions copying, like we do for
> process group, but I'm not sure if that would be too secure to do it,
> and if there would not be another similar resource in future.
>
> We can use CABA not only for CRIU for restoring processes, in normal
> life when processes detach CABA will help to understand from which place
> in process tree they were originally started from sshd/crond or
> something else.
>
> Hope my idea is not completely insane =)
>
> CC: Eric Biederman <ebiederm@xmission.com>
> CC: Kees Cook <keescook@chromium.org>
> CC: Alexander Viro <viro@zeniv.linux.org.uk>
> CC: Ingo Molnar <mingo@redhat.com>
> CC: Peter Zijlstra <peterz@infradead.org>
> CC: Juri Lelli <juri.lelli@redhat.com>
> CC: Vincent Guittot <vincent.guittot@linaro.org>
> CC: Dietmar Eggemann <dietmar.eggemann@arm.com>
> CC: Steven Rostedt <rostedt@goodmis.org>
> CC: Ben Segall <bsegall@google.com>
> CC: Mel Gorman <mgorman@suse.de>
> CC: Daniel Bristot de Oliveira <bristot@redhat.com>
> CC: Valentin Schneider <vschneid@redhat.com>
> CC: Andrew Morton <akpm@linux-foundation.org>
> CC: linux-ia64@vger.kernel.org
> CC: linux-kernel@vger.kernel.org
> CC: linux-mm@kvack.org
> CC: linux-fsdevel@vger.kernel.org
>
> Pavel Tikhomirov (2):
> Add CABA tree to task_struct
> tests: Add CABA selftest
>
> arch/ia64/kernel/mca.c | 3 +
> fs/exec.c | 1 +
> fs/proc/array.c | 18 +
> include/linux/sched.h | 7 +
> init/init_task.c | 3 +
> kernel/exit.c | 50 ++-
> kernel/fork.c | 4 +
> tools/testing/selftests/Makefile | 1 +
> tools/testing/selftests/caba/.gitignore | 1 +
> tools/testing/selftests/caba/Makefile | 7 +
> tools/testing/selftests/caba/caba_test.c | 501 +++++++++++++++++++++++
> tools/testing/selftests/caba/config | 1 +
> 12 files changed, 591 insertions(+), 6 deletions(-)
> create mode 100644 tools/testing/selftests/caba/.gitignore
> create mode 100644 tools/testing/selftests/caba/Makefile
> create mode 100644 tools/testing/selftests/caba/caba_test.c
> create mode 100644 tools/testing/selftests/caba/config
>
--
Best regards, Tikhomirov Pavel
Software Developer, Virtuozzo.
prev parent reply other threads:[~2022-06-10 16:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-10 16:32 Pavel Tikhomirov
2022-06-10 16:32 ` [PATCH 1/2] Add CABA tree to task_struct Pavel Tikhomirov
2022-06-10 21:02 ` kernel test robot
2022-06-10 16:32 ` [PATCH 2/2] tests: Add CABA selftest Pavel Tikhomirov
2022-06-10 16:38 ` Pavel Tikhomirov [this message]
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=cb7f3533-a904-ef0f-e3a9-39eed6775aad@virtuozzo.com \
--to=ptikhomirov@virtuozzo.com \
--cc=akpm@linux-foundation.org \
--cc=bristot@redhat.com \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=ebiederm@xmission.com \
--cc=juri.lelli@redhat.com \
--cc=keescook@chromium.org \
--cc=kernel@openvz.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=vincent.guittot@linaro.org \
--cc=viro@zeniv.linux.org.uk \
--cc=vschneid@redhat.com \
/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