From: Vince Weaver <vincent.weaver@maine.edu>
To: Vince Weaver <vincent.weaver@maine.edu>
Cc: Peter Zijlstra <peterz@infradead.org>,
Josh Poimboeuf <jpoimboe@redhat.com>,
Ingo Molnar <mingo@kernel.org>,
linux-kernel@vger.kernel.org, Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Andy Lutomirski <luto@kernel.org>
Subject: Re: perf: perf_fuzzer quickly locks up on 4.15-rc7
Date: Thu, 11 Jan 2018 15:43:41 -0500 (EST) [thread overview]
Message-ID: <alpine.DEB.2.21.1801111542160.23914@macbook-air> (raw)
In-Reply-To: <alpine.DEB.2.21.1801111455450.22460@macbook-air>
On Thu, 11 Jan 2018, Vince Weaver wrote:
> On Thu, 11 Jan 2018, Peter Zijlstra wrote:
>
> > On Thu, Jan 11, 2018 at 01:21:12PM -0600, Josh Poimboeuf wrote:
> > > Yuck. This time it was stack recursion on the entry stack. In the
> > > previous error, recursion was detected on the IRQ stack. Otherwise they
> > > look quite similar.
> > >
> > > Was that also with nopti?
> >
> > Both with pti enabled, nopti makes things work again.
>
> I think I have hit those errors even with pti disabled but now I'll have
> to double check.
I can confirm this, I am able to trigger the stack recursion warning even
when "pti=off" is set.
Jan 11 15:34:47 core2 kernel: [ 320.668900] WARNING: stack recursion on stack type 4
Jan 11 15:34:47 core2 kernel: [ 320.668909] WARNING: can't dereference registers at 00000000d5ae0491 for ip swapgs_restore_regs_and_return_to_usermode+0x28/0x7c
Vince
next prev parent reply other threads:[~2018-01-11 20:43 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-08 16:12 Vince Weaver
2018-01-08 17:30 ` Ingo Molnar
2018-01-08 20:29 ` Vince Weaver
2018-01-09 10:25 ` Peter Zijlstra
2018-01-09 13:26 ` Peter Zijlstra
2018-01-09 13:36 ` Peter Zijlstra
2018-01-09 13:44 ` Vince Weaver
2018-01-09 15:12 ` Peter Zijlstra
2018-01-09 15:24 ` Vince Weaver
2018-01-09 15:33 ` Peter Zijlstra
2018-01-09 15:56 ` Vince Weaver
2018-01-09 16:05 ` Peter Zijlstra
2018-01-09 17:07 ` Josh Poimboeuf
2018-01-11 5:25 ` Josh Poimboeuf
2018-01-11 19:00 ` Vince Weaver
2018-01-11 19:21 ` Josh Poimboeuf
2018-01-11 19:50 ` Peter Zijlstra
2018-01-11 19:57 ` Vince Weaver
2018-01-11 20:43 ` Vince Weaver [this message]
2018-05-01 13:29 ` perf: fuzzer causes stack going in wrong direction warnings Vince Weaver
2018-05-01 13:58 ` Josh Poimboeuf
2018-05-01 19:59 ` Vince Weaver
2018-05-01 22:04 ` Josh Poimboeuf
2018-05-02 20:50 ` Josh Poimboeuf
2018-05-04 14:35 ` Vince Weaver
2018-05-04 16:25 ` Josh Poimboeuf
2018-05-04 17:00 ` Vince Weaver
2018-05-05 15:38 ` Vince Weaver
2018-05-05 18:29 ` Josh Poimboeuf
2018-05-06 23:49 ` Josh Poimboeuf
2018-05-10 13:48 ` Peter Zijlstra
2018-05-10 14:27 ` Josh Poimboeuf
2018-05-10 23:16 ` Josh Poimboeuf
2018-01-09 16:16 ` perf: perf_fuzzer quickly locks up on 4.15-rc7 Ingo Molnar
2018-01-09 16:20 ` Peter Zijlstra
2018-01-09 17:18 ` Vince Weaver
2018-01-10 15:28 ` Vince Weaver
2018-01-09 16:14 ` Peter Zijlstra
2018-01-09 17:53 ` Steven Rostedt
2018-01-09 18:02 ` Peter Zijlstra
2018-01-09 18:09 ` Steven Rostedt
2018-01-09 19:53 ` Peter Zijlstra
2018-01-11 9:13 ` Peter Zijlstra
2018-01-11 15:26 ` Vince Weaver
2018-01-11 15:38 ` Peter Zijlstra
2018-01-11 16:41 ` Vince Weaver
2018-01-11 16:58 ` Vince Weaver
2018-01-11 17:03 ` Peter Zijlstra
2018-01-11 18:04 ` Vince Weaver
2018-01-11 18:20 ` Vince Weaver
2018-01-11 19:01 ` Peter Zijlstra
2018-01-11 19:11 ` Peter Zijlstra
2018-01-11 20:15 ` Vince Weaver
2018-01-11 20:40 ` Vince Weaver
2018-01-11 20:57 ` Peter Zijlstra
2018-01-12 19:48 ` Vince Weaver
2018-01-11 20:42 ` Peter Zijlstra
2018-01-11 15:29 ` Peter Zijlstra
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=alpine.DEB.2.21.1801111542160.23914@macbook-air \
--to=vincent.weaver@maine.edu \
--cc=acme@kernel.org \
--cc=jpoimboe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
/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®