linux-kernel - Arm64 defconfig-debug

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: <4aee8e37-b1f0-bd1c-9bf8-842c6cdc557e@quicinc.com>
Date:   Wed, 27 Oct 2021 15:45:32 -0400
From:   Qian Cai <quic_qiancai@...cinc.com>
To:     Catalin Marinas <catalin.marinas@....com>,
        Will Deacon <will@...nel.org>
CC:     <linux-arm-kernel@...ts.infradead.org>,
        <linux-kernel@...r.kernel.org>
Subject: Arm64 defconfig-debug

Hi there, some general debugging features like kmemleak, KASAN, lockdep,
UBSAN etc help fix many bugs 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 defconfig-debug available inside the
tree, so that it could amplify the general debugging/testing efforts for
arm64 across the broad.

The downside is that this might open a gate for other people to push yet
another subject-specific defconfig, but I don't see anything as
important as general debugging/testing at the moment. Then, there are
two defconfig need to be modified for some common changes, but I think
that is quite trivial to do. We could even create a simple script to
sync if that is not overkill.