[LU-4476] Add support for linux process namespace

• Status: Resolved
• Project: Lustre
• Affects Version/s: Lustre 2.6.0
• Fix Version/s: Lustre 2.6.0
• Type: Improvement
• Priority: Critical
• Reporter: James A Simmons
• Assignee: James Nunez (Inactive)
• Resolution: Fixed
• Labels: patch

Environment

Any system running a linux kernel at version 3.4 or higher using containter

Description

With linux kernels 3.4 and above a new vitalization methods were introduced. Part of the change is the ability to process to belong to distinct name spaces so each name space can't access resources in an other name space. Since each name space is separate but same the same kernel a mapping must be done between userland process identifiers and the kernels internal representation. This is to ensure all the kernel's internal values are unique. This ticket work is to ensure lustre supports this new feature.

Issue Links

• is related to: LU-4960 Investigate support for linux process...
• is related to: LU-5058 support for linux process namespace i...

Comments

[James A Simmons]

Patch at http://review.whamcloud.com/#/c/8817

[Peter Jones]

Thanks James!

[James Nunez (Inactive)]

James (Simmons),
The patch for client support of this feature has landed to master (2.6.0). From the patch comments, it looks like more work is needed for server support. Should we keep this ticket open for a patch for server support?

Thanks,
James

[Bob Glossman (Inactive)]

James (Nunez),
You are correct, the patch that has landed in master only has enough namespaces changes to support client only builds in newer kernels with CONFIG_UIDGID_STRICT_TYPE_CHECKS set. For sure a follow on patch is needed for server support. Until then the lack can be worked around by building & using server kernels without CONFIG_UIDGID_STRICT_TYPE_CHECKS set.

I think it's OK to keep this ticket open until we have a follow on patch for servers too.

[Jodi Levi (Inactive)]

James (Simmons),
Are you planning to create the necessary patch for server support?

[James A Simmons]

I had some discussions about what is needed for server side support. Some people feel this is all client side while others believe server side changes are needed. In order to know for sure we need to test on systems with namespaces enabled to test.

[Peter Jones]

James Simmons

Does it make sense to split the work to track the server side support into a separate ticket as it looks very likely that this work will miss 2.6 cutoff whereas the client-side changes have already landed?

Peter

[Jodi Levi (Inactive)]

Patch landed to Master. Any needed server side support will be tracked in LU-4690.