diff options
| author | Sargun Dhillon <sargun@sargun.me> | 2020-11-12 13:09:52 +0300 |
|---|---|---|
| committer | Trond Myklebust <trond.myklebust@hammerspace.com> | 2020-12-02 22:05:54 +0300 |
| commit | d3ff46fe693683cb9660e9b93e8c932cc8e0c1f8 (patch) | |
| tree | 8bf2bcf2ef734f5a0d43dda4d4e8c9271b98e00b /net/bridge | |
| parent | d18a9d3fa0f27a47706fb67f1ee0f4d971587c4e (diff) | |
| download | linux-d3ff46fe693683cb9660e9b93e8c932cc8e0c1f8.tar.xz | |
NFSv4: Refactor to use user namespaces for nfs4idmap
In several patches work has been done to enable NFSv4 to use user
namespaces:
58002399da65: NFSv4: Convert the NFS client idmapper to use the container user namespace
3b7eb5e35d0f: NFS: When mounting, don't share filesystems between different user namespaces
Unfortunately, the userspace APIs were only such that the userspace facing
side of the filesystem (superblock s_user_ns) could be set to a non init
user namespace. This furthers the fs_context related refactoring, and
piggybacks on top of that logic, so the superblock user namespace, and the
NFS user namespace are the same.
Users can still use rpc.idmapd if they choose to, but there are complexities
with user namespaces and request-key that have yet to be addresssed.
Eventually, we will need to at least:
* Come up with an upcall mechanism that can be triggered inside of the container,
or safely triggered outside, with the requisite context to do the right
mapping. * Handle whatever refactoring needs to be done in net/sunrpc.
Signed-off-by: Sargun Dhillon <sargun@sargun.me>
Tested-by: Alban Crequy <alban.crequy@gmail.com>
Fixes: 62a55d088cd8 ("NFS: Additional refactoring for fs_context conversion")
Signed-off-by: Trond Myklebust <trond.myklebust@hammerspace.com>
Diffstat (limited to 'net/bridge')
0 files changed, 0 insertions, 0 deletions