From: Eric Biggers <ebiggers3@gmail.com>
To: Dmitry Vyukov <dvyukov@google.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
Steven Rostedt <rostedt@goodmis.org>,
syzbot
<syzbot+c9695f0404c72c8f0b7abbac660d986af9008fc5@syzkaller.appspotmail.com>,
LKML <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@redhat.com>,
syzkaller-bugs@googlegroups.com
Subject: Re: possible deadlock in perf_trace_destroy (2)
Date: Sat, 21 Apr 2018 10:12:25 -0700 [thread overview]
Message-ID: <20180421171225.GA1098@sol.localdomain> (raw)
In-Reply-To: <CACT4Y+bJ7U_ehBFEVWpvo6rwnT8-oto3c4b=VSyZyv92Y0E=tw@mail.gmail.com>
On Tue, Jan 23, 2018 at 08:37:49AM +0100, 'Dmitry Vyukov' via syzkaller-bugs wrote:
> On Tue, Jan 23, 2018 at 12:19 AM, Peter Zijlstra <peterz@infradead.org> wrote:
> > On Mon, Jan 22, 2018 at 05:20:13PM -0500, Steven Rostedt wrote:
> >>
> >> Peter,
> >>
> >> Isn't this the same as what you mentioned (and had a hack patch for)
> >> before?
> >>
> >> http://lkml.kernel.org/r/20180109133651.GB2369@hirez.programming.kicks-ass.net
> >>
> >
> > Looks like it. Just haven't managed to get those patches merged. I'll
> > try and get that sorted tomorrow. Thanks for the reminder.
>
No longer occurring, fix was commit 82d94856fa22:
#syz fix: perf/core: Fix lock inversion between perf,trace,cpuhp
- Eric
prev parent reply other threads:[~2018-04-21 17:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-07 11:39 possible deadlock in perf_trace_destroy (2) syzbot
2017-11-07 11:41 ` Dmitry Vyukov
2018-01-22 20:57 ` syzbot
2018-01-22 22:20 ` Steven Rostedt
2018-01-22 23:19 ` Peter Zijlstra
2018-01-23 7:37 ` Dmitry Vyukov
2018-04-21 17:12 ` Eric Biggers [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=20180421171225.GA1098@sol.localdomain \
--to=ebiggers3@gmail.com \
--cc=dvyukov@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=syzbot+c9695f0404c72c8f0b7abbac660d986af9008fc5@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.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.