Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
MIME-Version: 1.0
References: <962c0565-89a3-c6d2-37e0-a93c8c753d57@quicinc.com>
In-Reply-To: <962c0565-89a3-c6d2-37e0-a93c8c753d57@quicinc.com>
From:   Masahiro Yamada <masahiroy@kernel.org>
Date:   Thu, 28 Oct 2021 23:03:54 +0900
Message-ID: <CAK7LNAQX2GiUB04fOm7p=F+H5p9XFQjt9hEPSZS4JR+FZK6PZg@mail.gmail.com>
Subject: Re: Introduce "make debugconfig"
To:     Qian Cai <quic_qiancai@quicinc.com>
Cc:     Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Content-Type: text/plain; charset="UTF-8"
Precedence: bulk

On Thu, Oct 28, 2021 at 10:32 PM Qian Cai <quic_qiancai@quicinc.com> wrote:
>
> 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

Please do not wire it up to 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.


-- 
Best Regards
Masahiro Yamada