From: Greg KH <gregkh@linuxfoundation.org>
To: Jiri Slaby <jslaby@suse.com>
Cc: syzbot <syzbot+26183d9746e62da329b8@syzkaller.appspotmail.com>,
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: possible deadlock in tty_unthrottle
Date: Fri, 28 Feb 2020 15:34:36 +0100 [thread overview]
Message-ID: <20200228143436.GB3054483@kroah.com> (raw)
In-Reply-To: <6590a26d-8234-67a8-16e0-6391da6765d9@suse.com>
On Fri, Feb 28, 2020 at 02:34:48PM +0100, Jiri Slaby wrote:
> On 27. 02. 20, 9:39, syzbot wrote:
> > Hello,
> >
> > syzbot found the following crash on:
> >
> > HEAD commit: f8788d86 Linux 5.6-rc3 git tree: upstream
> > console output:
> > https://syzkaller.appspot.com/x/log.txt?x=1102d22de00000 kernel
> > config: https://syzkaller.appspot.com/x/.config?x=5d2e033af114153f
> > dashboard link:
> > https://syzkaller.appspot.com/bug?extid=26183d9746e62da329b8
> > compiler: clang version 10.0.0
> > (https://github.com/llvm/llvm-project/
> > c2443155a0fb245c8f17f2c1c72b6ea391e86e81)
> >
> > 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+26183d9746e62da329b8@syzkaller.appspotmail.com
>
> So trying below, but there is no reproducer for the issue, so I am not
> sure if it triggers any action at all.
>
> #syz test:
> git://git.kernel.org/pub/scm/linux/kernel/git/jirislaby/linux.git vc_sel
Ah, yeah, no reproducer :(
Ok, I'll queue these up and see what happens, thanks!
greg k-h
next prev parent reply other threads:[~2020-02-28 14:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-27 8:39 possible deadlock in tty_unthrottle syzbot
2020-02-28 13:34 ` Jiri Slaby
2020-02-28 13:34 ` syzbot
2020-02-28 14:34 ` Greg KH [this message]
[not found] <20200227113622.4716-1-hdanton@sina.com>
2020-02-27 11:40 ` Jiri Slaby
2020-02-28 10:04 ` Jiri Slaby
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=20200228143436.GB3054483@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=jslaby@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+26183d9746e62da329b8@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;
as well as URLs for NNTP newsgroup(s).