Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
From:   Kees Cook <keescook@chromium.org>
To:     Jann Horn <jannh@google.com>
Cc:     Kees Cook <keescook@chromium.org>,
        Nathan Chancellor <nathan@kernel.org>,
        linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ubsan: Clarify Kconfig text for CONFIG_UBSAN_TRAP
Date:   Wed,  5 Jul 2023 15:07:34 -0700
Message-Id: <168859485210.800831.2317943820956176004.b4-ty@chromium.org>
In-Reply-To: <20230705215128.486054-1-jannh@google.com>
References: <20230705215128.486054-1-jannh@google.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Precedence: bulk


On Wed, 05 Jul 2023 23:51:27 +0200, Jann Horn wrote:
> Make it clearer in the one-line description and the verbose description
> text that CONFIG_UBSAN_TRAP as currently implemented involves a tradeoff of
> much less helpful oops messages in exchange for a smaller kernel image.
> (With the additional effect of turning UBSAN warnings into crashes, which
> may or may not be desired.)
> 
> 
> [...]

Applied with some tweaks to wording, thanks!

[1/1] ubsan: Clarify Kconfig text for CONFIG_UBSAN_TRAP
      https://git.kernel.org/kees/c/a2dbac607873

-- 
Kees Cook