From: Kees Cook <keescook@chromium.org>
To: kernel test robot <yujie.liu@intel.com>
Cc: lkp@lists.01.org, lkp@intel.com, linux-kernel@vger.kernel.org,
linux-hardening@vger.kernel.org,
"Gustavo A. R. Silva" <gustavoars@kernel.org>
Subject: Re: [fortify] 54d9469bc5: WARNING:at_fs/nfs/namespace.c:#nfs_d_automount
Date: Mon, 10 Oct 2022 23:54:01 -0700 [thread overview]
Message-ID: <202210102352.B80BC62@keescook> (raw)
In-Reply-To: <202210110948.26b43120-yujie.liu@intel.com>
On Tue, Oct 11, 2022 at 11:45:56AM +0800, kernel test robot wrote:
> FYI, we noticed the following commit (built with gcc-11):
>
> commit: 54d9469bc515dc5fcbc20eecbe19cea868b70d68 ("fortify: Add run-time WARN for cross-field memcpy()")
> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master
>
> [...]
> [ 57.256986][ T4357] memcpy: detected field-spanning write (size 28) of single field "&ctx->nfs_server.address" at fs/nfs/namespace.c:178 (size 16)
Thanks for the report! I've sent a patch for this now:
https://lore.kernel.org/lkml/20221011065243.583650-1-keescook@chromium.org/
--
Kees Cook
prev parent reply other threads:[~2022-10-11 6:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-11 3:45 [fortify] 54d9469bc5: WARNING:at_fs/nfs/namespace.c:#nfs_d_automount kernel test robot
2022-10-11 6:54 ` Kees Cook [this message]
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=202210102352.B80BC62@keescook \
--to=keescook@chromium.org \
--cc=gustavoars@kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=lkp@lists.01.org \
--cc=yujie.liu@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox