tracing/user_events: Initial support for grouping
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest1 patch 0 repliesNew
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/1 | tracing/user_events: Move pages/locks into groups to prepare for namespaceskernel/ | +274 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/1] tracing/user_events: Initial support for grouping
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:
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.
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
Signature · 1 line
2.25.1