From: Kees Cook <keescook@chromium.org>
To: kernel test robot <rong.a.chen@intel.com>
Cc: David Windsor <dave@nullcore.net>,
linux-sctp@vger.kernel.org,
Network Development <netdev@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>, LKP <lkp@01.org>
Subject: Re: [LKP] ab9ee8e38b [ 22.890412] WARNING: CPU: 0 PID: 632 at mm/usercopy.c:81 usercopy_warn
Date: Sun, 19 Aug 2018 22:31:44 -0700 [thread overview]
Message-ID: <CAGXu5jLHq_i-w2Tc75hkzV1VMO45vGyxsP=+670PLTiGEG7Acg@mail.gmail.com> (raw)
In-Reply-To: <20180820005204.GB31827@shao2-debian>
On Sun, Aug 19, 2018 at 5:52 PM, kernel test robot
<rong.a.chen@intel.com> wrote:
> [ 22.855033] Bad or missing usercopy whitelist? Kernel memory overwrite attempt detected to SLUB object 'SCTP' (offset 1332, size 4)!
For this .config, pahole reports 1332 as the offset of the whitelist,
so I'm not sure what's happening here. It's as if no whitelist was
used when building the cache?
I'm still trying to build a reproducers...
-Kees
--
Kees Cook
Pixel Security
prev parent reply other threads:[~2018-08-20 5:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-20 0:52 [LKP] ab9ee8e38b [ 22.890412] WARNING: CPU: 0 PID: 632 at mm/usercopy.c:81 usercopy_warn kernel test robot
2018-08-20 5:31 ` 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='CAGXu5jLHq_i-w2Tc75hkzV1VMO45vGyxsP=+670PLTiGEG7Acg@mail.gmail.com' \
--to=keescook@chromium.org \
--cc=dave@nullcore.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sctp@vger.kernel.org \
--cc=lkp@01.org \
--cc=netdev@vger.kernel.org \
--cc=rong.a.chen@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;
as well as URLs for NNTP newsgroup(s).