From: Peter Zijlstra <peterz@infradead.org>
To: syzbot
<bot+2af19c9e1ffe4d4ee1d16c56ae7580feaee75765@syzkaller.appspotmail.com>
Cc: dvhart@infradead.org, linux-kernel@vger.kernel.org,
mingo@redhat.com, syzkaller-bugs@googlegroups.com,
tglx@linutronix.de
Subject: Re: WARNING in get_pi_state
Date: Tue, 31 Oct 2017 11:31:34 +0100 [thread overview]
Message-ID: <20171031103134.2cik6ycsaytptfhy@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <20171031101853.xpfh72y643kdfhjs@hirez.programming.kicks-ass.net>
On Tue, Oct 31, 2017 at 11:18:53AM +0100, Peter Zijlstra wrote:
> On Tue, Oct 31, 2017 at 09:36:44AM +0100, Peter Zijlstra wrote:
> > On Mon, Oct 30, 2017 at 12:44:00PM -0700, syzbot wrote:
> > > WARNING: CPU: 1 PID: 24353 at kernel/futex.c:818 get_pi_state+0x15b/0x190
> > > kernel/futex.c:818
> >
> > > exit_pi_state_list+0x556/0x7a0 kernel/futex.c:932
> > > mm_release+0x46d/0x590 kernel/fork.c:1191
> > > exit_mm kernel/exit.c:499 [inline]
> > > do_exit+0x481/0x1b00 kernel/exit.c:852
> > > SYSC_exit kernel/exit.c:937 [inline]
> > > SyS_exit+0x22/0x30 kernel/exit.c:935
> > > entry_SYSCALL_64_fastpath+0x1f/0xbe
> >
> >
> > Argh, I definitely messed that up. Let me have a prod..
>
> The below appears to cure the problem, I could (fairly quickly)
> reproduce the issue one I hacked up the repro.c to not bother with
> tunnels.
>
> With the below patch, the reproducer has been running for a fairly long
> time now without issue.
And of course, now it went *splat*, lemme continue staring..
next prev parent reply other threads:[~2017-10-31 10:31 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-30 19:44 syzbot
2017-10-30 19:53 ` Dmitry Vyukov
2017-10-31 8:36 ` Peter Zijlstra
2017-10-31 10:18 ` Peter Zijlstra
2017-10-31 10:31 ` Peter Zijlstra [this message]
2017-10-31 10:38 ` Peter Zijlstra
2017-11-01 8:45 ` Peter Zijlstra
2017-11-07 16:16 ` Dmitry Vyukov
2017-10-31 12:06 ` [tip:core/urgent] futex: Fix more put_pi_state() vs. exit_pi_state_list() races tip-bot for Peter Zijlstra
2017-10-31 22:11 ` Thomas Gleixner
2017-11-01 8:05 ` Ingo Molnar
2017-11-01 8:09 ` tip-bot for Peter Zijlstra
2017-10-31 9:16 ` WARNING in get_pi_state Peter Zijlstra
2017-10-31 9:29 ` Dmitry Vyukov
2017-10-31 10:08 ` Peter Zijlstra
2017-10-31 10:21 ` Dmitry Vyukov
2017-10-31 10:23 ` Dmitry Vyukov
2017-10-31 10:36 ` Peter Zijlstra
2017-11-07 14:50 ` Dmitry Vyukov
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=20171031103134.2cik6ycsaytptfhy@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=bot+2af19c9e1ffe4d4ee1d16c56ae7580feaee75765@syzkaller.appspotmail.com \
--cc=dvhart@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=syzkaller-bugs@googlegroups.com \
--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®