[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <202210290029.3CD089A86C@keescook>
Date: Sat, 29 Oct 2022 00:32:14 -0700
From: Kees Cook <keescook@...omium.org>
To: Gwan-gyeong Mun <gwan-gyeong.mun@...el.com>
Cc: airlied@...ux.ie, trix@...hat.com, dlatypov@...gle.com,
dri-devel@...ts.freedesktop.org, linux-kernel@...r.kernel.org,
linux-hardening@...r.kernel.org, linux-sparse@...r.kernel.org,
llvm@...ts.linux.dev, arnd@...nel.org,
intel-gfx@...ts.freedesktop.org, nathan@...nel.org,
rodrigo.vivi@...el.com, mchehab@...nel.org,
tvrtko.ursulin@...ux.intel.com, mauro.chehab@...ux.intel.com,
ndesaulniers@...gle.com, gustavoars@...nel.org, vitor@...saru.org,
luc.vanoostenryck@...il.com
Subject: Re: [PATCH v5] overflow: Introduce overflows_type() and
castable_to_type()
On Sat, Oct 29, 2022 at 08:55:43AM +0300, Gwan-gyeong Mun wrote:
> Hi Kees,
Hi! :)
> I've updated to v5 with the last comment of Nathan.
> Could you please kindly review what more is needed as we move forward with
> this patch?
It looks fine to me -- I assume it'll go via the drm tree? Would you
rather I carry the non-drm changes in my tree instead?
>
--
Kees Cook
Powered by blists - more mailing lists