public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
To: Dmitry Vyukov <dvyukov@google.com>
Cc: syzbot <syzbot+831ee52a258e90882b4d@syzkaller.appspotmail.com>,
	LKML <linux-kernel@vger.kernel.org>,
	Petr Mladek <pmladek@suse.com>,
	Steven Rostedt <rostedt@goodmis.org>,
	Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
	syzkaller-bugs <syzkaller-bugs@googlegroups.com>
Subject: Re: possible deadlock in vprintk_emit
Date: Fri, 8 Jun 2018 16:55:40 +0900	[thread overview]
Message-ID: <20180608075540.GA636@jagdpanzerIV> (raw)
In-Reply-To: <CACT4Y+aPPuC+VopRpfJj41TBiN5ke-gVdQCBvD5ohxsXmz=hbA@mail.gmail.com>

On (06/08/18 09:50), Dmitry Vyukov wrote:
> > Hello,
> >
> > syzbot found the following crash on:
> >
> > HEAD commit:    1c8c5a9d38f6 Merge git://git.kernel.org/pub/scm/linux/kern..
> > git tree:       upstream
> > console output: https://syzkaller.appspot.com/x/log.txt?x=131d4ddf800000
> > kernel config:  https://syzkaller.appspot.com/x/.config?x=4f1acdf888c9d4e9
> > dashboard link: https://syzkaller.appspot.com/bug?extid=831ee52a258e90882b4d
> > compiler:       gcc (GCC) 8.0.1 20180413 (experimental)
> >
> > Unfortunately, I don't have any reproducer for this crash yet.
> >
> > IMPORTANT: if you fix the bug, please add the following tag to the commit:
> > Reported-by: syzbot+831ee52a258e90882b4d@syzkaller.appspotmail.com
> 
> 
> This is the same as that one, right?

Yes.

	-ss

      reply	other threads:[~2018-06-08  7:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-08  7:38 possible deadlock in vprintk_emit syzbot
2018-06-08  7:50 ` Dmitry Vyukov
2018-06-08  7:55   ` Sergey Senozhatsky [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=20180608075540.GA636@jagdpanzerIV \
    --to=sergey.senozhatsky.work@gmail.com \
    --cc=dvyukov@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pmladek@suse.com \
    --cc=rostedt@goodmis.org \
    --cc=sergey.senozhatsky@gmail.com \
    --cc=syzbot+831ee52a258e90882b4d@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox