From: syzbot <syzbot+0b7c8bfd17c00d016fb4@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, elver@google.com, glider@google.com,
gregkh@linuxfoundation.org, jirislaby@kernel.org,
john.ogness@linutronix.de, linux-kernel@vger.kernel.org,
npiggin@gmail.com, pmladek@suse.com, rdunlap@infradead.org,
rostedt@goodmis.org, senozhatsky@chromium.org,
swboyd@chromium.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] possible deadlock in console_unlock (2)
Date: Sun, 26 Jun 2022 01:04:10 -0700 [thread overview]
Message-ID: <00000000000095e3d105e2553f0a@google.com> (raw)
In-Reply-To: <000000000000dab76c05d0bc284c@google.com>
syzbot suspects this issue was fixed by commit:
commit faebd693c59387b7b765fab64b543855e15a91b4
Author: John Ogness <john.ogness@linutronix.de>
Date: Thu Apr 21 21:22:36 2022 +0000
printk: rename cpulock functions
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=17ed359bf00000
start commit: aa051d36ce4a Merge tag 'for-linus-2022052401' of git://git..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=6c31e1555a4c59f3
dashboard link: https://syzkaller.appspot.com/bug?extid=0b7c8bfd17c00d016fb4
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=16a5aad6f00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=16d697c3f00000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: printk: rename cpulock functions
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2022-06-26 8:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-14 9:17 [syzbot] possible deadlock in console_unlock (2) syzbot
2022-06-26 8:04 ` syzbot [this message]
2022-06-27 7:11 ` Dmitry Vyukov
2022-06-27 7:39 ` Sergey Senozhatsky
2022-06-27 7:42 ` Dmitry Vyukov
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=00000000000095e3d105e2553f0a@google.com \
--to=syzbot+0b7c8bfd17c00d016fb4@syzkaller.appspotmail.com \
--cc=akpm@linux-foundation.org \
--cc=elver@google.com \
--cc=glider@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=jirislaby@kernel.org \
--cc=john.ogness@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=npiggin@gmail.com \
--cc=pmladek@suse.com \
--cc=rdunlap@infradead.org \
--cc=rostedt@goodmis.org \
--cc=senozhatsky@chromium.org \
--cc=swboyd@chromium.org \
--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