-
Notifications
You must be signed in to change notification settings - Fork 5.2k
add CONFIG_F2FS_FS_SECURITY=y #2778
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Do you have any numbers for the impact this has on memory requriements and overall CPU performance impact? |
I don't have a comparative test for the memory usage and CPU performance with and without the feature enabled in the kernel, but I have a Pi with this enabled, which did not had it prior, and I do not see a noticeable difference in feel. |
Did a quick recompile with this enabled - adds 352 bytes on the Pi4 zImage. Looking at the code, cannot see if having much of a effect on the performance, and it's only used when f2fs is being use I believe. So seems like an OK addition. |
Okay. |
@dom Not yet enabled - do we intend to do so? |
If f2fs is intended to be usable for root filesystem, it makes sense for it to have feature parity with ext4 where possible. Currently, CONFIG_F2FS_FS_SECURITY appears to be the only config option missing:
As a specific example, F2FS_FS_SECURITY enables the use of
|
This does indeed add very little code:
In fact the extra seems to get swallowed up in such a way that the memory map doesn't expand. ext4 has exactly the same initialisation hook, but it configures a different set of attributes. Since the code size change is negligible, and any (presumably tiny) runtime overhead only affects F2FS users (who might benefit from the change) I'm prepared to enable the config setting. |
Add a negligible amount of core kernel code for capability-based access control on F2FS. See: raspberrypi#2778 Signed-off-by: Phil Elwell <[email protected]>
See #4637. |
Add a negligible amount of core kernel code for capability-based access control on F2FS. See: #2778 Signed-off-by: Phil Elwell <[email protected]>
Add a negligible amount of core kernel code for capability-based access control on F2FS. See: #2778 Signed-off-by: Phil Elwell <[email protected]>
Add a negligible amount of core kernel code for capability-based access control on F2FS. See: #2778 Signed-off-by: Phil Elwell <[email protected]>
Add a negligible amount of core kernel code for capability-based access control on F2FS. See: #2778 Signed-off-by: Phil Elwell <[email protected]>
Add a negligible amount of core kernel code for capability-based access control on F2FS. See: #2778 Signed-off-by: Phil Elwell <[email protected]>
Add a negligible amount of core kernel code for capability-based access control on F2FS. See: #2778 Signed-off-by: Phil Elwell <[email protected]>
Add a negligible amount of core kernel code for capability-based access control on F2FS. See: #2778 Signed-off-by: Phil Elwell <[email protected]>
commit b255b04ec51f85a74593ccc2e3e8a82e4227913a from https://github.com/raspberrypi/linux.git rpi-5.15.y Add a negligible amount of core kernel code for capability-based access control on F2FS. See: raspberrypi/linux#2778 Signed-off-by: Phil Elwell <[email protected]> Signed-off-by: Meng Li <[email protected]>
Add a negligible amount of core kernel code for capability-based access control on F2FS. See: #2778 Signed-off-by: Phil Elwell <[email protected]>
Add a negligible amount of core kernel code for capability-based access control on F2FS. See: #2778 Signed-off-by: Phil Elwell <[email protected]>
Add a negligible amount of core kernel code for capability-based access control on F2FS. See: #2778 Signed-off-by: Phil Elwell <[email protected]>
Add a negligible amount of core kernel code for capability-based access control on F2FS. See: #2778 Signed-off-by: Phil Elwell <[email protected]>
Add a negligible amount of core kernel code for capability-based access control on F2FS. See: #2778 Signed-off-by: Phil Elwell <[email protected]>
Add a negligible amount of core kernel code for capability-based access control on F2FS. See: #2778 Signed-off-by: Phil Elwell <[email protected]>
Add a negligible amount of core kernel code for capability-based access control on F2FS. See: #2778 Signed-off-by: Phil Elwell <[email protected]>
Add a negligible amount of core kernel code for capability-based access control on F2FS. See: #2778 Signed-off-by: Phil Elwell <[email protected]>
Add a negligible amount of core kernel code for capability-based access control on F2FS. See: #2778 Signed-off-by: Phil Elwell <[email protected]>
Add a negligible amount of core kernel code for capability-based access control on F2FS. See: #2778 Signed-off-by: Phil Elwell <[email protected]>
Add a negligible amount of core kernel code for capability-based access control on F2FS. See: #2778 Signed-off-by: Phil Elwell <[email protected]>
Add a negligible amount of core kernel code for capability-based access control on F2FS. See: #2778 Signed-off-by: Phil Elwell <[email protected]>
Add a negligible amount of core kernel code for capability-based access control on F2FS. See: #2778 Signed-off-by: Phil Elwell <[email protected]>
Add a negligible amount of core kernel code for capability-based access control on F2FS. See: #2778 Signed-off-by: Phil Elwell <[email protected]>
Add a negligible amount of core kernel code for capability-based access control on F2FS. See: #2778 Signed-off-by: Phil Elwell <[email protected]>
Add a negligible amount of core kernel code for capability-based access control on F2FS. See: #2778 Signed-off-by: Phil Elwell <[email protected]>
Add a negligible amount of core kernel code for capability-based access control on F2FS. See: #2778 Signed-off-by: Phil Elwell <[email protected]>
Add a negligible amount of core kernel code for capability-based access control on F2FS. See: #2778 Signed-off-by: Phil Elwell <[email protected]>
Add a negligible amount of core kernel code for capability-based access control on F2FS. See: #2778 Signed-off-by: Phil Elwell <[email protected]>
Add a negligible amount of core kernel code for capability-based access control on F2FS. See: #2778 Signed-off-by: Phil Elwell <[email protected]>
Very good. I've just upgraded to the latest kernel (raspberrypi-kernel 1:1.20220120-1) and it is working as expected:
|
Add a negligible amount of core kernel code for capability-based access control on F2FS. See: #2778 Signed-off-by: Phil Elwell <[email protected]>
Add a negligible amount of core kernel code for capability-based access control on F2FS. See: #2778 Signed-off-by: Phil Elwell <[email protected]>
Add a negligible amount of core kernel code for capability-based access control on F2FS. See: #2778 Signed-off-by: Phil Elwell <[email protected]>
Add a negligible amount of core kernel code for capability-based access control on F2FS. See: #2778 Signed-off-by: Phil Elwell <[email protected]>
Add a negligible amount of core kernel code for capability-based access control on F2FS. See: #2778 Signed-off-by: Phil Elwell <[email protected]>
Add a negligible amount of core kernel code for capability-based access control on F2FS. See: #2778 Signed-off-by: Phil Elwell <[email protected]>
Add a negligible amount of core kernel code for capability-based access control on F2FS. See: #2778 Signed-off-by: Phil Elwell <[email protected]>
Add a negligible amount of core kernel code for capability-based access control on F2FS. See: #2778 Signed-off-by: Phil Elwell <[email protected]>
Add a negligible amount of core kernel code for capability-based access control on F2FS. See: #2778 Signed-off-by: Phil Elwell <[email protected]>
Add a negligible amount of core kernel code for capability-based access control on F2FS. See: #2778 Signed-off-by: Phil Elwell <[email protected]>
Add a negligible amount of core kernel code for capability-based access control on F2FS. See: #2778 Signed-off-by: Phil Elwell <[email protected]>
Add a negligible amount of core kernel code for capability-based access control on F2FS. See: raspberrypi#2778 Signed-off-by: Phil Elwell <[email protected]>
Add a negligible amount of core kernel code for capability-based access control on F2FS. See: raspberrypi/linux#2778 Signed-off-by: Phil Elwell <[email protected]>
BugLink: https://bugs.launchpad.net/bugs/1958146 Add a negligible amount of core kernel code for capability-based access control on F2FS. See: raspberrypi/linux#2778 Signed-off-by: Phil Elwell <[email protected]> (cherry picked from commit bab33ae95bfc61f665599bc190ada426b3c79643 rpi-5.15.y) Signed-off-by: Juerg Haefliger <[email protected]>
Uh oh!
There was an error while loading. Please reload this page.
I think the CONFIG_F2FS_FS_SECURITY=y option should be enabled in the kernel.
It enables support for the XATTR security namespace, which atm is not supported due to this option currently not being set to yes.
The xattr security namespace is used by SELinux and is also a requirement for Samba4 AD/DC full support.
We already have XATTR and POSIX_ACL support enabled for F2FS, with user namespace support, it only makes sense to fully support XATTR on F2FS by also enabling CONFIG_F2FS_FS_SECURITY.
XATTR F2FS support added following: #2508
Thank you.
The text was updated successfully, but these errors were encountered: