From: syzbot <syzbot+43e93968b964e369db0b@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, gregkh@linuxfoundation.org,
jslaby@suse.com, linux-kernel@vger.kernel.org,
linux-serial@vger.kernel.org, penguin-kernel@I-love.SAKURA.ne.jp,
pmladek@suse.com, rostedt@goodmis.org,
sergey.senozhatsky.work@gmail.com, sergey.senozhatsky@gmail.com,
syzkaller-bugs@googlegroups.com, threeearcat@gmail.com
Subject: Re: possible deadlock in console_unlock
Date: Sun, 24 Nov 2019 18:41:01 -0800 [thread overview]
Message-ID: <000000000000b8c995059822b10d@google.com> (raw)
In-Reply-To: <00000000000087008b056df8fbb3@google.com>
syzbot has bisected this bug to:
commit b6da31b2c07c46f2dcad1d86caa835227a16d9ff
Author: DaeRyong Jeong <threeearcat@gmail.com>
Date: Mon Apr 30 15:27:04 2018 +0000
tty: Fix data race in tty_insert_flip_string_fixed_flag
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=12d9bc0ee00000
start commit: 0ad39cb3 Merge tag 'kconfig-v4.18' of git://git.kernel.org..
git tree: upstream
final crash: https://syzkaller.appspot.com/x/report.txt?x=11d9bc0ee00000
console output: https://syzkaller.appspot.com/x/log.txt?x=16d9bc0ee00000
kernel config: https://syzkaller.appspot.com/x/.config?x=b9a1f3aa8b8ddd16
dashboard link: https://syzkaller.appspot.com/bug?extid=43e93968b964e369db0b
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=14c89b9f800000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=167f596f800000
Reported-by: syzbot+43e93968b964e369db0b@syzkaller.appspotmail.com
Fixes: b6da31b2c07c ("tty: Fix data race in
tty_insert_flip_string_fixed_flag")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2019-11-25 2:41 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-06 13:17 possible deadlock in console_unlock syzbot
2018-06-07 4:44 ` syzbot
2018-06-07 5:10 ` Sergey Senozhatsky
2018-06-07 11:00 ` Petr Mladek
2018-06-07 11:40 ` Tetsuo Handa
2018-06-07 14:03 ` Sergey Senozhatsky
2018-06-07 14:01 ` Sergey Senozhatsky
2018-06-08 8:18 ` Petr Mladek
2018-06-15 8:38 ` Sergey Senozhatsky
2018-06-19 8:04 ` Petr Mladek
2018-06-19 8:08 ` Sergey Senozhatsky
2019-02-20 10:52 ` Tetsuo Handa
2019-11-25 2:41 ` syzbot [this message]
2019-02-16 6:36 Yao HongBo
2019-02-16 7:21 ` Sergey Senozhatsky
2019-02-16 7:46 ` Sergey Senozhatsky
2019-02-16 7:59 ` Yao HongBo
2019-02-18 5:46 ` Sergey Senozhatsky
2019-02-18 12:09 ` Yao HongBo
2019-02-18 14:07 ` Yao HongBo
2019-02-19 1:32 ` Sergey Senozhatsky
2019-02-19 2:48 ` Yao HongBo
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=000000000000b8c995059822b10d@google.com \
--to=syzbot+43e93968b964e369db0b@syzkaller.appspotmail.com \
--cc=akpm@linux-foundation.org \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=penguin-kernel@I-love.SAKURA.ne.jp \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=sergey.senozhatsky.work@gmail.com \
--cc=sergey.senozhatsky@gmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=threeearcat@gmail.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).