Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::3:5 as permitted sender) client-ip=2620:137:e000::3:5;
From:   Kees Cook <keescook@chromium.org>
To:     Stephen Boyd <swboyd@chromium.org>
Cc:     Kees Cook <keescook@chromium.org>, linux-kernel@vger.kernel.org,
        patches@lists.linux.dev, Arnd Bergmann <arnd@arndb.de>,
        Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
        Alexander Potapenko <glider@google.com>,
        Marco Elver <elver@google.com>,
        Dmitry Vyukov <dvyukov@google.com>,
        Andrew Morton <akpm@linux-foundation.org>,
        kasan-dev@googlegroups.com
Subject: Re: [PATCH v2] lkdtm: Add kfence read after free crash type
Date:   Thu, 30 Nov 2023 14:05:45 -0800
Message-Id: <170138194305.3650163.16392122923355361827.b4-ty@chromium.org>
In-Reply-To: <20231129214413.3156334-1-swboyd@chromium.org>
References: <20231129214413.3156334-1-swboyd@chromium.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Precedence: bulk

On Wed, 29 Nov 2023 13:44:04 -0800, Stephen Boyd wrote:
> Add the ability to allocate memory from kfence and trigger a read after
> free on that memory to validate that kfence is working properly. This is
> used by ChromeOS integration tests to validate that kfence errors can be
> collected on user devices and parsed properly.
> 
> 

Applied to for-next/hardening, thanks!

[1/1] lkdtm: Add kfence read after free crash type
      https://git.kernel.org/kees/c/0e689e666214

Take care,

-- 
Kees Cook