From: "Gustavo A. R. Silva" <gustavoars@kernel.org>
To: kernel test robot <oliver.sang@intel.com>
Cc: Kees Cook <keescook@chromium.org>,
lkp@lists.01.org, lkp@intel.com, linux-hardening@vger.kernel.org,
Arnd Bergmann <arnd@arndb.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Shuah Khan <shuah@kernel.org>,
Nathan Chancellor <nathan@kernel.org>,
Nick Desaulniers <ndesaulniers@google.com>,
Tom Rix <trix@redhat.com>,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
llvm@lists.linux.dev
Subject: Re: [fortify] 728833277d: WARNING:at_net/netlink/af_netlink.c:#netlink_ack
Date: Wed, 7 Sep 2022 08:39:19 +0100 [thread overview]
Message-ID: <YxhKp4n7K4h3aMQt@work> (raw)
In-Reply-To: <202209071317.245c5751-oliver.sang@intel.com>
On Wed, Sep 07, 2022 at 01:42:16PM +0800, kernel test robot wrote:
Hi!
>
> Hi Kees Cook,
>
> the patch "[PATCH 1/2] fortify: Add run-time WARN for cross-field memcpy()"
> raises a persistent WARNING as below report in our tests.
>
> according to commit message, we understand this is kind of expected. but
> we don't have enough knowledge if it reveals a real issue in kernel source
> code and what the next step could be.
>
> so we still report FYI.
>
> if you think it's unnecessary for us to make out this kind of report, please
> let us know. we will consider how to refine our report rules. Thanks a lot!
>
> below is the full report.
It seems that the idea is to continue reporting these warnings, as they
help us identify the places that need to be audited and determine how to
refactor the code (in case it's a false positive), or how to properly fix
it (in case it's an actual bug).
In this case, it seems that the issue was already addressed by this patch:
https://lore.kernel.org/linux-hardening/20220903043749.3102675-1-keescook@chromium.org/
Thanks
--
Gustavo
next prev parent reply other threads:[~2022-09-07 7:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-01 6:59 [PATCH 0/2] fortify: Add run-time WARN for cross-field memcpy() Kees Cook
2022-09-01 6:59 ` [PATCH 1/2] " Kees Cook
2022-09-07 5:42 ` [fortify] 728833277d: WARNING:at_net/netlink/af_netlink.c:#netlink_ack kernel test robot
2022-09-07 7:39 ` Gustavo A. R. Silva [this message]
2022-09-07 7:49 ` Oliver Sang
2022-09-01 6:59 ` [PATCH 2/2] lkdtm: Update tests for memcpy() run-time warnings Kees Cook
2022-09-01 20:05 ` [PATCH 0/2] fortify: Add run-time WARN for cross-field memcpy() Nathan Chancellor
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=YxhKp4n7K4h3aMQt@work \
--to=gustavoars@kernel.org \
--cc=arnd@arndb.de \
--cc=gregkh@linuxfoundation.org \
--cc=keescook@chromium.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=lkp@intel.com \
--cc=lkp@lists.01.org \
--cc=llvm@lists.linux.dev \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=oliver.sang@intel.com \
--cc=shuah@kernel.org \
--cc=trix@redhat.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