From: Jiri Olsa <jolsa@redhat.com>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: Adrian Hunter <adrian.hunter@intel.com>,
Jiri Olsa <jolsa@kernel.org>, Wang Nan <wangnan0@huawei.com>,
Josh Poimboeuf <jpoimboe@redhat.com>,
Kees Cook <keescook@chromium.org>,
Namhyung Kim <namhyung@kernel.org>,
Ingo Molnar <mingo@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: perf test "object code reading" segfaulting via usercopy check
Date: Sun, 11 Sep 2016 05:16:06 +0200 [thread overview]
Message-ID: <20160911031606.GA2025@krava> (raw)
In-Reply-To: <20160909154720.GF32585@kernel.org>
On Fri, Sep 09, 2016 at 12:47:20PM -0300, Arnaldo Carvalho de Melo wrote:
> Em Fri, Sep 09, 2016 at 05:41:25PM +0200, Jiri Olsa escreveu:
> > On Fri, Sep 09, 2016 at 12:36:26PM -0300, Arnaldo Carvalho de Melo wrote:
> > > Hi Adrian,
> > >
> > > I noticed that 'perf test "object code reading"' is segfaulting
> > > here:
> > >
> > > [root@jouet linux]# perf test -F "object code reading"
> > > 21: Test object code reading :Segmentation fault
> > > [root@jouet linux]#
> > >
> > > dmesg output below, trying to figure this out...
> >
> > heya,
> > it's the new hardened user copy check.. I sent patches for that:
> >
> > http://marc.info/?l=linux-kernel&m=147332143929289&w=2
> > http://marc.info/?l=linux-kernel&m=147332145229291&w=2
>
> Cool, but that is for the kernel, without thinking too much about it, is
> there a way to change that 'perf test' entry to avoid doing what
> triggers the segfault?
>
> My first thought was that it was reading 4K all the way to the end,
> where it should instead read just what is remaining, but I haven't
> checked this theory at all.
it's actually reading within the bounds of kernel text that triggers
that, it's the new CONFIG_HARDENED_USERCOPY feature:
f5509cc18daa mm: Hardened usercopy
check the change log, there's list of conditions and
one of them is:
- object must not overlap with kernel text
jirka
prev parent reply other threads:[~2016-09-11 3:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-09 15:36 perf test "object code reading" segfaulting via usercopy check Arnaldo Carvalho de Melo
2016-09-09 15:41 ` Jiri Olsa
2016-09-09 15:47 ` Arnaldo Carvalho de Melo
2016-09-11 3:16 ` Jiri Olsa [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=20160911031606.GA2025@krava \
--to=jolsa@redhat.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=jolsa@kernel.org \
--cc=jpoimboe@redhat.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung@kernel.org \
--cc=wangnan0@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.