lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <962c0565-89a3-c6d2-37e0-a93c8c753d57@quicinc.com>
Date:   Thu, 28 Oct 2021 09:32:51 -0400
From:   Qian Cai <quic_qiancai@...cinc.com>
To:     Masahiro Yamada <masahiroy@...nel.org>
CC:     <linux-kbuild@...r.kernel.org>, <linux-kernel@...r.kernel.org>
Subject: Introduce "make debugconfig"

Hi there, some general debugging features like kmemleak, KASAN, lockdep,

UBSAN etc help fix many viruses like a microscope. On the other hand, those
 features are scatter around and mixed up with more situational debugging
 options making them difficult to consume properly.



Since I have been deal with those options on a daily basis for the last

a few years and accumulated the knowledge of their pros and cons, I am

thinking about to create an initial "make debugconfig" target, so that
it could amplify the general debugging/testing efforts and help
establish sensitive default values for those options across the broad.


The idea is to have a debugconfig inside kernel/configs/ and update
scripts/kconfig/Makefile and Documentation/admin-guide/README.rst
accordingly. I am still trying to figure out a few implementation
details like how to convert an existing .config to debugconfig, but want
to gather some feedback before I dive in too deep.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ