From: syzbot <syzbot+3cc1054e15babd5f4cd2@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, 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_lock_spinning_enable (2)
Date: Sat, 18 Jun 2022 20:47:07 -0700 [thread overview]
Message-ID: <00000000000071951f05e1c4d7c8@google.com> (raw)
In-Reply-To: <0000000000007ba8cd05d0c1c3b0@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=17d0607bf00000
start commit: bc403203d65a Merge tag 'powerpc-5.18-5' of git://git.kerne..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=78013caa620443d6
dashboard link: https://syzkaller.appspot.com/bug?extid=3cc1054e15babd5f4cd2
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=14c08966f00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=108132e9f00000
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-19 3:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-14 15:58 [syzbot] possible deadlock in console_lock_spinning_enable (2) syzbot
2021-12-10 20:24 ` syzbot
2022-06-19 3:47 ` syzbot [this message]
2022-06-20 5:44 ` Sergey Senozhatsky
2022-06-20 8:16 ` Dmitry Vyukov
2022-06-20 9:24 ` Sergey Senozhatsky
2022-06-20 11:28 ` Dmitry Vyukov
[not found] <20220619074222.197-1-hdanton@sina.com>
2022-06-19 9:46 ` syzbot
[not found] <20220619121654.313-1-hdanton@sina.com>
2022-06-19 12:35 ` syzbot
[not found] <20220619133032.381-1-hdanton@sina.com>
2022-06-19 16:42 ` syzbot
[not found] <20220620104728.501-1-hdanton@sina.com>
2022-06-20 11:10 ` syzbot
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=00000000000071951f05e1c4d7c8@google.com \
--to=syzbot+3cc1054e15babd5f4cd2@syzkaller.appspotmail.com \
--cc=akpm@linux-foundation.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.