[LU-9578] having security_dentry_init_security doesn't mean it's enabled

• Type: Bug
• Resolution: Fixed
• Priority: Minor
• Fix Version/s: Lustre 2.11.0, Lustre 2.10.2
• Affects Version/s: Lustre 2.10.0
• Severity: 3
• Assignee: Alex Zhuravlev
• Reporter: Alex Zhuravlev

Description

LU-8956 introduced security context support, but Lustre stops to work if the corresponding feature is not enabled in the kernel.

Issue Links

• is duplicated by: LU-10130 mkdir returns -95 EOPNOTSUPP with 2.10.1 on sles 12 sp3 with CONFIG_SECURITY disabled

Comments

[Gerrit Updater]

Minh Diep ([e-mail]) uploaded a new patch: https://review.whamcloud.com/29737
Subject: LU-9578 llite: use security context if it's enabled in the kernel
Project: fs/lustre-release
Branch: b2_10
Current Patch Set: 1
Commit: 4ceed178648772ca6f169e6fc535e79dc82c4799

[Peter Jones]

Landed for 2.11

[Gerrit Updater]

Oleg Drokin ([e-mail]) merged in patch https://review.whamcloud.com/27364/
Subject: LU-9578 llite: use security context if it's enabled in the kernel
Project: fs/lustre-release
Branch: master
Current Patch Set:
Commit: 61f26ea47f96632a90702f2b404e845a01498612

[Alex Zhuravlev]

right, CONFIG_SECURITY is not defined in my setup. i'm getting -95 in many cases like file creations.

[John Hammond]

Alex, are you building Lustre on a kernel without CONFIG_SECURITY? Could you describe the error/behavior that you see?

[Gerrit Updater]

Alex Zhuravlev ([e-mail]) uploaded a new patch: https://review.whamcloud.com/27364
Subject: LU-9578 llite: use security context if it's enabled in the kernel
Project: fs/lustre-release
Branch: master
Current Patch Set: 1
Commit: 2ceabf014b5e48a4ed287bf9048d8f20a1b374e1