linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Petr Mladek <pmladek@suse.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: syzbot <syzbot+d1fe9b7b917f2715c7d4@syzkaller.appspotmail.com>,
	linux-kernel@vger.kernel.org, rostedt@goodmis.org,
	sergey.senozhatsky@gmail.com, syzkaller-bugs@googlegroups.com,
	Andy Lutomirski <luto@kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Borislav Petkov <bp@alien8.de>, "H. Peter Anvin" <hpa@zytor.com>,
	Ingo Molnar <mingo@kernel.org>,
	x86@kernel.org, Dmitry Vyukov <dvyukov@google.com>,
	Eric Dumazet <edumazet@google.com>
Subject: Re: general protection fault in try_to_wake_up
Date: Tue, 3 Apr 2018 11:29:03 +0200	[thread overview]
Message-ID: <20180403092902.i2xg3dmdlcv477aw@pathway.suse.cz> (raw)
In-Reply-To: <20180403091333.GZ4082@hirez.programming.kicks-ass.net>

On Tue 2018-04-03 11:13:33, Peter Zijlstra wrote:
> On Tue, Apr 03, 2018 at 10:50:03AM +0200, Petr Mladek wrote:
> > raw_spin_lock() succeeded here. Therefore lockdep was still working
> > at this stage.
> 
> What does the success of raw_spin_lock() have to do with lockdep ?

It means that also lockdep succeeded there. Therefore the general
protection fault in __lock_acquire() was specific to the spinlock
taken by try_to_wake_up(). I though that it might had been an useful
information.

Anyway, the other replay from Dmitry suggested that it was a known
bug, see
https://lkml.kernel.org/r/CACT4Y+ZJ2QD7MPy4hB-M=mz2LuVu3bRbLg1QdY=z=+Su1QWMqg@mail.gmail.com

Best Regards,
Petr

      reply	other threads:[~2018-04-03  9:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-29 16:01 general protection fault in try_to_wake_up syzbot
2018-03-29 16:32 ` Steven Rostedt
2018-03-29 16:53   ` Dmitry Vyukov
2018-03-31 15:58     ` Dmitry Vyukov
2018-04-03  8:50 ` Petr Mladek
2018-04-03  8:56   ` Petr Mladek
2018-04-03  9:13   ` Peter Zijlstra
2018-04-03  9:29     ` Petr Mladek [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=20180403092902.i2xg3dmdlcv477aw@pathway.suse.cz \
    --to=pmladek@suse.com \
    --cc=bp@alien8.de \
    --cc=dvyukov@google.com \
    --cc=edumazet@google.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@kernel.org \
    --cc=mingo@kernel.org \
    --cc=peterz@infradead.org \
    --cc=rostedt@goodmis.org \
    --cc=sergey.senozhatsky@gmail.com \
    --cc=syzbot+d1fe9b7b917f2715c7d4@syzkaller.appspotmail.com \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.org \
    /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).