From: Kees Cook <keescook@chromium.org>
To: Xiu Jianfeng <xiujianfeng@huawei.com>
Cc: linux-kernel@vger.kernel.org, eparis@redhat.com,
wangweiyang2@huawei.com, linux-audit@redhat.com,
linux-hardening@vger.kernel.org
Subject: Re: [PATCH -next] audit: use struct_size() helper in kmalloc()
Date: Tue, 14 Dec 2021 09:08:39 -0800 [thread overview]
Message-ID: <202112140908.80D89AC9@keescook> (raw)
In-Reply-To: <20211214114854.133328-1-xiujianfeng@huawei.com>
On Tue, Dec 14, 2021 at 07:48:54PM +0800, Xiu Jianfeng wrote:
> Make use of struct_size() helper instead of an open-coded calucation.
>
> Link: https://github.com/KSPP/linux/issues/160
> Signed-off-by: Xiu Jianfeng <xiujianfeng@huawei.com>
Reviewed-by: Kees Cook <keescook@chromium.org>
--
Kees Cook
--
Linux-audit mailing list
Linux-audit@redhat.com
https://listman.redhat.com/mailman/listinfo/linux-audit
WARNING: multiple messages have this Message-ID (diff)
From: Kees Cook <keescook@chromium.org>
To: Xiu Jianfeng <xiujianfeng@huawei.com>
Cc: paul@paul-moore.com, eparis@redhat.com, linux-audit@redhat.com,
linux-kernel@vger.kernel.org, wangweiyang2@huawei.com,
linux-hardening@vger.kernel.org
Subject: Re: [PATCH -next] audit: use struct_size() helper in kmalloc()
Date: Tue, 14 Dec 2021 09:08:39 -0800 [thread overview]
Message-ID: <202112140908.80D89AC9@keescook> (raw)
In-Reply-To: <20211214114854.133328-1-xiujianfeng@huawei.com>
On Tue, Dec 14, 2021 at 07:48:54PM +0800, Xiu Jianfeng wrote:
> Make use of struct_size() helper instead of an open-coded calucation.
>
> Link: https://github.com/KSPP/linux/issues/160
> Signed-off-by: Xiu Jianfeng <xiujianfeng@huawei.com>
Reviewed-by: Kees Cook <keescook@chromium.org>
--
Kees Cook
next prev parent reply other threads:[~2021-12-14 17:08 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-14 11:48 [PATCH -next] audit: use struct_size() helper in kmalloc() Xiu Jianfeng
2021-12-14 11:48 ` Xiu Jianfeng
2021-12-14 17:08 ` Kees Cook [this message]
2021-12-14 17:08 ` Kees Cook
2021-12-14 17:54 ` Gustavo A. R. Silva
2021-12-14 17:54 ` Gustavo A. R. Silva
2021-12-14 18:10 ` Gustavo A. R. Silva
2021-12-14 18:10 ` Gustavo A. R. Silva
2021-12-15 2:55 ` xiujianfeng
2021-12-15 2:55 ` xiujianfeng
2021-12-15 2:54 ` xiujianfeng
2021-12-15 2:54 ` xiujianfeng
2021-12-14 22:47 ` Paul Moore
2021-12-14 22:47 ` Paul Moore
2021-12-15 2:56 ` xiujianfeng
2021-12-15 2:56 ` 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=202112140908.80D89AC9@keescook \
--to=keescook@chromium.org \
--cc=eparis@redhat.com \
--cc=linux-audit@redhat.com \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=wangweiyang2@huawei.com \
--cc=xiujianfeng@huawei.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.