Skip to content
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

Config change in 5.19.X #71

Closed
Churam opened this issue Aug 31, 2022 · 3 comments
Closed

Config change in 5.19.X #71

Churam opened this issue Aug 31, 2022 · 3 comments

Comments

@Churam
Copy link

Churam commented Aug 31, 2022

Hello,

The X86_SMAP option is no longer present in 5.19.X kernels. It is now enforced.
( commit )

Since it has been removed, the script mark the entry as failed.

[+] Special report mode: show_fail
[+] Kconfig file to check: /opt/KERNEL/linux-5.19.5/.config
[+] Detected architecture: X86_64
[+] Detected kernel version: 5.19
=========================================================================================================================
              option name               | type  |desired val | decision |      reason      | check result
=========================================================================================================================
CONFIG_X86_SMAP                         |kconfig|     y      |defconfig | self_protection  | FAIL: not found

The GCC_PLUGIN_RANDSTRUCT and GCC_PLUGIN_RANDSTRUCT_PERFORMANCE have changed now that CLANG has the feature. ( commit ). They are now nammed RANDSTRUCT_FULL and RANDSTRUCT_PERFORMANCE respectively.

At the moment they don't fail but the new entries should be added in the script I think.

 grep RANDSTRUCT ./.config
# CONFIG_RANDSTRUCT_NONE is not set
CONFIG_RANDSTRUCT_FULL=y
# CONFIG_RANDSTRUCT_PERFORMANCE is not set
CONFIG_RANDSTRUCT=y
CONFIG_GCC_PLUGIN_RANDSTRUCT=y
a13xp0p0v added a commit that referenced this issue Sep 2, 2022
a13xp0p0v added a commit that referenced this issue Sep 2, 2022
@a13xp0p0v
Copy link
Owner

Hi @Churam,

Thanks for your report!

I've improved the checks, please have a look.

@anthraxx
Copy link
Contributor

anthraxx commented Sep 6, 2022

maybe it would make sense to tag a new release after 🐱

@a13xp0p0v
Copy link
Owner

Hi @anthraxx,

I have a complex and time-consuming procedure for preparing the kconfig-hardened-check releases.

I’m planning to do this work for the next Linux kernel release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants