-
Notifications
You must be signed in to change notification settings - Fork 105
[Deepin-Kernel-SIG] [linux-6.6.y] config: Enable LIST_HARDENED #481
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
Conversation
Linux kernel 6.6 introduced CONFIG_LIST_HARDENED, of which CONFIG_DEBUG_LIST is a superset [1]. Since CONFIG_DEBUG_LIST selects CONFIG_LIST_HARDENED, configs that already selected CONFIG_DEBUG_LIST were not prompted for CONFIG_LIST_HARDENED. Since CONFIG_DEBUG_LIST has never been designed with performance in mind, non-debug kernels should prefer CONFIG_LIST_HARDENED. The main benefit is improved performance; the only downside is slightly worse error reporting (the WARNING is turned into an access fault in some cases). Hardening-wise there is no functional difference. [1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=aebc7b0d8d91bbc69e976909963046bc48bca4fd Link: https://gitlab.archlinux.org/archlinux/packaging/packages/linux/-/issues/26
Linux kernel 6.6 introduced CONFIG_LIST_HARDENED, of which CONFIG_DEBUG_LIST is a superset [1]. Since CONFIG_DEBUG_LIST selects CONFIG_LIST_HARDENED, configs that already selected CONFIG_DEBUG_LIST were not prompted for CONFIG_LIST_HARDENED. Since CONFIG_DEBUG_LIST has never been designed with performance in mind, non-debug kernels should prefer CONFIG_LIST_HARDENED. The main benefit is improved performance; the only downside is slightly worse error reporting (the WARNING is turned into an access fault in some cases). Hardening-wise there is no functional difference. [1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=aebc7b0d8d91bbc69e976909963046bc48bca4fd Link: https://gitlab.archlinux.org/archlinux/packaging/packages/linux/-/issues/26
Linux kernel 6.6 introduced CONFIG_LIST_HARDENED, of which CONFIG_DEBUG_LIST is a superset [1]. Since CONFIG_DEBUG_LIST selects CONFIG_LIST_HARDENED, configs that already selected CONFIG_DEBUG_LIST were not prompted for CONFIG_LIST_HARDENED. Since CONFIG_DEBUG_LIST has never been designed with performance in mind, non-debug kernels should prefer CONFIG_LIST_HARDENED. The main benefit is improved performance; the only downside is slightly worse error reporting (the WARNING is turned into an access fault in some cases). Hardening-wise there is no functional difference. [1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=aebc7b0d8d91bbc69e976909963046bc48bca4fd Link: https://gitlab.archlinux.org/archlinux/packaging/packages/linux/-/issues/26
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
Linux kernel 6.6 introduced CONFIG_LIST_HARDENED, of which CONFIG_DEBUG_LIST is a superset [1]. Since CONFIG_DEBUG_LIST selects CONFIG_LIST_HARDENED, configs that already selected CONFIG_DEBUG_LIST were not prompted for CONFIG_LIST_HARDENED. Since CONFIG_DEBUG_LIST has never been designed with performance in mind, non-debug kernels should prefer CONFIG_LIST_HARDENED. The main benefit is improved performance; the only downside is slightly worse error reporting (the WARNING is turned into an access fault in some cases). Hardening-wise there is no functional difference. [1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=aebc7b0d8d91bbc69e976909963046bc48bca4fd Link: https://gitlab.archlinux.org/archlinux/packaging/packages/linux/-/issues/26 Link: deepin-community#481 (cherry picked from commit 8960594) Signed-off-by: Wentao Guan <guanwentao@uniontech.com> Conflicts: arch/x86/configs/deepin_x86_desktop_defconfig
Linux kernel 6.6 introduced CONFIG_LIST_HARDENED, of which CONFIG_DEBUG_LIST is a superset [1]. Since CONFIG_DEBUG_LIST selects CONFIG_LIST_HARDENED, configs that already selected CONFIG_DEBUG_LIST were not prompted for CONFIG_LIST_HARDENED. Since CONFIG_DEBUG_LIST has never been designed with performance in mind, non-debug kernels should prefer CONFIG_LIST_HARDENED. The main benefit is improved performance; the only downside is slightly worse error reporting (the WARNING is turned into an access fault in some cases). Hardening-wise there is no functional difference. [1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=aebc7b0d8d91bbc69e976909963046bc48bca4fd Link: https://gitlab.archlinux.org/archlinux/packaging/packages/linux/-/issues/26 Link: deepin-community#481 (cherry picked from commit e3901ac) Signed-off-by: Wentao Guan <guanwentao@uniontech.com>
Linux kernel 6.6 introduced CONFIG_LIST_HARDENED, of which CONFIG_DEBUG_LIST is a superset [1]. Since CONFIG_DEBUG_LIST selects CONFIG_LIST_HARDENED, configs that already selected CONFIG_DEBUG_LIST were not prompted for CONFIG_LIST_HARDENED. Since CONFIG_DEBUG_LIST has never been designed with performance in mind, non-debug kernels should prefer CONFIG_LIST_HARDENED. The main benefit is improved performance; the only downside is slightly worse error reporting (the WARNING is turned into an access fault in some cases). Hardening-wise there is no functional difference. [1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=aebc7b0d8d91bbc69e976909963046bc48bca4fd Link: https://gitlab.archlinux.org/archlinux/packaging/packages/linux/-/issues/26 Link: deepin-community#481 (cherry picked from commit 8cf38f6) Signed-off-by: Wentao Guan <guanwentao@uniontech.com>
Linux kernel 6.6 introduced CONFIG_LIST_HARDENED, of which CONFIG_DEBUG_LIST is a superset [1]. Since CONFIG_DEBUG_LIST selects CONFIG_LIST_HARDENED, configs that already selected CONFIG_DEBUG_LIST were not prompted for CONFIG_LIST_HARDENED. Since CONFIG_DEBUG_LIST has never been designed with performance in mind, non-debug kernels should prefer CONFIG_LIST_HARDENED. The main benefit is improved performance; the only downside is slightly worse error reporting (the WARNING is turned into an access fault in some cases). Hardening-wise there is no functional difference. [1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=aebc7b0d8d91bbc69e976909963046bc48bca4fd Link: https://gitlab.archlinux.org/archlinux/packaging/packages/linux/-/issues/26 Link: deepin-community#481 (cherry picked from commit 8960594) Signed-off-by: Wentao Guan <guanwentao@uniontech.com> Conflicts: arch/x86/configs/deepin_x86_desktop_defconfig
Linux kernel 6.6 introduced CONFIG_LIST_HARDENED, of which CONFIG_DEBUG_LIST is a superset [1]. Since CONFIG_DEBUG_LIST selects CONFIG_LIST_HARDENED, configs that already selected CONFIG_DEBUG_LIST were not prompted for CONFIG_LIST_HARDENED. Since CONFIG_DEBUG_LIST has never been designed with performance in mind, non-debug kernels should prefer CONFIG_LIST_HARDENED. The main benefit is improved performance; the only downside is slightly worse error reporting (the WARNING is turned into an access fault in some cases). Hardening-wise there is no functional difference. [1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=aebc7b0d8d91bbc69e976909963046bc48bca4fd Link: https://gitlab.archlinux.org/archlinux/packaging/packages/linux/-/issues/26 Link: deepin-community#481 (cherry picked from commit e3901ac) Signed-off-by: Wentao Guan <guanwentao@uniontech.com>
Linux kernel 6.6 introduced CONFIG_LIST_HARDENED, of which CONFIG_DEBUG_LIST is a superset [1]. Since CONFIG_DEBUG_LIST selects CONFIG_LIST_HARDENED, configs that already selected CONFIG_DEBUG_LIST were not prompted for CONFIG_LIST_HARDENED. Since CONFIG_DEBUG_LIST has never been designed with performance in mind, non-debug kernels should prefer CONFIG_LIST_HARDENED. The main benefit is improved performance; the only downside is slightly worse error reporting (the WARNING is turned into an access fault in some cases). Hardening-wise there is no functional difference. [1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=aebc7b0d8d91bbc69e976909963046bc48bca4fd Link: https://gitlab.archlinux.org/archlinux/packaging/packages/linux/-/issues/26 Link: deepin-community#481 (cherry picked from commit 8cf38f6) Signed-off-by: Wentao Guan <guanwentao@uniontech.com>
Linux kernel 6.6 introduced CONFIG_LIST_HARDENED, of which CONFIG_DEBUG_LIST is a superset [1]. Since CONFIG_DEBUG_LIST selects CONFIG_LIST_HARDENED, configs that already selected CONFIG_DEBUG_LIST were not prompted for CONFIG_LIST_HARDENED.
Since CONFIG_DEBUG_LIST has never been designed with performance in mind, non-debug kernels should prefer CONFIG_LIST_HARDENED. The main benefit is improved performance; the only downside is slightly worse error reporting (the WARNING is turned into an access fault in some cases). Hardening-wise there is no functional difference.
[1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=aebc7b0d8d91bbc69e976909963046bc48bca4fd
Link: https://gitlab.archlinux.org/archlinux/packaging/packages/linux/-/issues/26