user namespaces: introduction
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest6 patches 13 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/6 | user namespaces: introduce user_struct->user_namespace relationshipinclude/ include/ kernel/ +1 more | +20 | 2 replies | |
| 2/6 | user namespaces: move user_ns from nsproxy into user structinclude/ include/ include/ +8 more | +45 | 2 replies | |
| 3/6 | user namespaces: rig generic_permission for simple userns checkfs/ | +13 | 0 replies | |
| 4/6 | user namespaces: add user_ns to super blockfs/ fs/ include/ | +12 | 9 replies | |
| 5/6 | user namespaces: refuse create in other user_nsfs/ | +6 | 0 replies | |
| 6/6 | user_namespace: move put_user_ns outside lockkernel/ | +1 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/6] user namespaces: introduction
Following is a set of user namespace patches I've been playing with this week.
The first two patches are I believe fixes which should go in regardless of which direction user namespaces take.
The rest of the patches are one approach to providing default cross-userns isolation for files. Any filesystem can provide its own intelligent cross-userns userid equivalence checks by defining its own permission function, which is what Eric and I have been talking about doing.
The next step is probably to handle some of the task-to-task cross-userns checks.
Comments appreciated.
thanks,
-serge