From: Johannes Berg <johannes@sipsolutions.net>
To: Kees Cook <keescook@chromium.org>,
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>,
Hawkins Jiawei <yin31149@gmail.com>,
linux-wireless@vger.kernel.org
Subject: Re: [fortify] 54d9469bc5: WARNING:at_net/wireless/wext-core.c:#wireless_send_event
Date: Tue, 11 Oct 2022 08:59:49 +0200 [thread overview]
Message-ID: <0d8be2bcb891a56c42760c8e955877841046458b.camel@sipsolutions.net> (raw)
In-Reply-To: <202210102312.1CC8197@keescook>
On Mon, 2022-10-10 at 23:17 -0700, Kees Cook wrote:
> On Tue, Oct 11, 2022 at 11:46:21AM +0800, kernel test robot wrote:
> > commit: 54d9469bc515dc5fcbc20eecbe19cea868b70d68 ("fortify: Add run-time WARN for cross-field memcpy()")
> > https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master
> > [...]
> > caused below changes (please refer to attached dmesg/kmsg for entire log/backtrace):
> > [...]
> > [ 95.913726][ T36] memcpy: detected field-spanning write (size 16) of single field "&compat_event->pointer" at net/wireless/wext-core.c:623 (size 4)
>
> This was fixed with:
> e3e6e1d16a4c ("wifi: wext: use flex array destination for memcpy()")
>
> I expect this will land before -rc1 closes, but Johannes will know more
> about the schedule.
>
Yes, we're planning to send a pull request today, so that should go to
Linus with the net pull request tomorrow.
johannes
prev parent reply other threads:[~2022-10-11 7:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-11 3:46 kernel test robot
2022-10-11 6:17 ` Kees Cook
2022-10-11 6:59 ` Johannes Berg [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=0d8be2bcb891a56c42760c8e955877841046458b.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=gustavoars@kernel.org \
--cc=keescook@chromium.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=lkp@intel.com \
--cc=lkp@lists.01.org \
--cc=yin31149@gmail.com \
--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
all inboxes | Powered by JetHome®