[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <202112072125.AC79323201@keescook>
Date: Tue, 7 Dec 2021 21:27:47 -0800
From: Kees Cook <keescook@...omium.org>
To: Xiu Jianfeng <xiujianfeng@...wei.com>
Cc: akpm@...ux-foundation.org, laniel_francis@...vacyrequired.com,
andriy.shevchenko@...ux.intel.com, adobriyan@...il.com,
linux@...ck-us.net, andreyknvl@...il.com, dja@...ens.net,
ast@...nel.org, daniel@...earbox.net, andrii@...nel.org,
kafai@...com, songliubraving@...com, yhs@...com,
john.fastabend@...il.com, kpsingh@...nel.org,
linux-kernel@...r.kernel.org, netdev@...r.kernel.org,
bpf@...r.kernel.org
Subject: Re: [PATCH -next 0/2] Introduce memset_range() helper for wiping
members
On Wed, Dec 08, 2021 at 11:04:49AM +0800, Xiu Jianfeng wrote:
> Xiu Jianfeng (2):
> string.h: Introduce memset_range() for wiping members
For doing a memset range, the preferred method is to use
a struct_group in the structure itself. This makes the range
self-documenting, and allows the compile to validate the exact size,
makes it addressable, etc. The other memset helpers are for "everything
to the end", which doesn't usually benefit from the struct_group style
of range declaration.
> bpf: use memset_range helper in __mark_reg_known
I never saw this patch arrive on the list?
--
Kees Cook
Powered by blists - more mailing lists