From: Kees Cook <keescook@chromium.org>
To: Xiu Jianfeng <xiujianfeng@huawei.com>
Cc: akpm@linux-foundation.org, laniel_francis@privacyrequired.com,
andriy.shevchenko@linux.intel.com, adobriyan@gmail.com,
linux@roeck-us.net, andreyknvl@gmail.com, dja@axtens.net,
ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
kafai@fb.com, songliubraving@fb.com, yhs@fb.com,
john.fastabend@gmail.com, kpsingh@kernel.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
bpf@vger.kernel.org
Subject: Re: [PATCH -next 0/2] Introduce memset_range() helper for wiping members
Date: Tue, 7 Dec 2021 21:27:47 -0800 [thread overview]
Message-ID: <202112072125.AC79323201@keescook> (raw)
In-Reply-To: <20211208030451.219751-1-xiujianfeng@huawei.com>
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
next prev parent reply other threads:[~2021-12-08 5:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-08 3:04 [PATCH -next 0/2] Introduce memset_range() helper for wiping members Xiu Jianfeng
2021-12-08 3:04 ` [PATCH -next 1/2] string.h: Introduce memset_range() " Xiu Jianfeng
2021-12-08 4:28 ` Andrew Morton
2021-12-08 10:30 ` xiujianfeng
2021-12-08 23:44 ` Andrew Morton
2021-12-09 5:17 ` Kees Cook
2021-12-09 6:29 ` xiujianfeng
2021-12-09 6:29 ` xiujianfeng
2021-12-08 17:12 ` Alexey Dobriyan
2021-12-08 3:04 ` [PATCH -next 2/2] bpf: use memset_range helper in __mark_reg_known Xiu Jianfeng
2021-12-08 5:27 ` Kees Cook [this message]
2021-12-08 10:30 ` [PATCH -next 0/2] Introduce memset_range() helper for wiping members xiujianfeng
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=202112072125.AC79323201@keescook \
--to=keescook@chromium.org \
--cc=adobriyan@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=andreyknvl@gmail.com \
--cc=andrii@kernel.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=dja@axtens.net \
--cc=john.fastabend@gmail.com \
--cc=kafai@fb.com \
--cc=kpsingh@kernel.org \
--cc=laniel_francis@privacyrequired.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=netdev@vger.kernel.org \
--cc=songliubraving@fb.com \
--cc=xiujianfeng@huawei.com \
--cc=yhs@fb.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.