linux-trace-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Beau Belgrave <beaub@linux.microsoft.com>
To: rostedt@goodmis.org, mhiramat@kernel.org,
	mathieu.desnoyers@efficios.com, brauner@kernel.org,
	stefanb@linux.ibm.com
Cc: linux-trace-devel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/1] tracing/user_events: Initial support for grouping
Date: Fri, 30 Sep 2022 17:10:15 -0700	[thread overview]
Message-ID: <20221001001016.2832-1-beaub@linux.microsoft.com> (raw)

In order to enable namespaces, or any sort of isolation, within
user_events the register lock and pages need to be broken up into
groups. Each event and file now has a group pointer which stores
the actual pages to map, lookup data and synchronization objects.

There's been some previous discussion about this both in the
tracefs meetings as well as on the mailing lists:
Link: https://lore.kernel.org/all/20220312010140.1880-1-beaub@linux.microsoft.com/
Link: https://lore.kernel.org/all/20220425184631.2068-1-beaub@linux.microsoft.com/

This was also brought up in the most recent plumbers conference,
with some feedback to follow the IMA namespace model. This only enables
a single group that maps to init_user_ns, as IMA namespace has done.

Link: https://youtu.be/zai3gvpuEHc?t=4403
Link: https://lore.kernel.org/linux-kernel/20220915193221.1728029-15-stefanb@linux.ibm.com/#t

While it's not clear what all needs to be within a tracing namespace,
we have to start somewhere. The patch leaves out how new namespaces
are created and further configured by an operator. However, it
offers a structure and the minimum scaffolding to enable isolation
while we discuss this in further detail and build upon this in steps.

Beau Belgrave (1):
  tracing/user_events: Move pages/locks into groups to prepare for
    namespaces

 kernel/trace/trace_events_user.c | 346 ++++++++++++++++++++++++-------
 1 file changed, 274 insertions(+), 72 deletions(-)


base-commit: c23cbf0d23145ffd0f99520a5c1d65abba628936
-- 
2.25.1


             reply	other threads:[~2022-10-01  0:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-01  0:10 Beau Belgrave [this message]
2022-10-01  0:10 ` [PATCH 1/1] tracing/user_events: Move pages/locks into groups to prepare for namespaces Beau Belgrave

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=20221001001016.2832-1-beaub@linux.microsoft.com \
    --to=beaub@linux.microsoft.com \
    --cc=brauner@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-trace-devel@vger.kernel.org \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=mhiramat@kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=stefanb@linux.ibm.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;
as well as URLs for NNTP newsgroup(s).