From: syzbot <syzbot+007bfe0f3330f6e1e7d1@syzkaller.appspotmail.com>
To: bp@alien8.de, christian.koenig@amd.com,
dri-devel@lists.freedesktop.org, gustavo@padovan.org,
hdanton@sina.com, hpa@zytor.com, jmattson@google.com,
joro@8bytes.org, kvm@vger.kernel.org,
linaro-mm-sig-bounces@lists.linaro.org,
linaro-mm-sig@lists.linaro.org, linux-kernel@vger.kernel.org,
linux-media@vger.kernel.org, mark.rutland@arm.com,
mingo@redhat.com, pbonzini@redhat.com, peterz@infradead.org,
seanjc@google.com, sumit.semwal@linaro.org,
syzkaller-bugs@googlegroups.com, tglx@linutronix.de,
vkuznets@redhat.com, wanpengli@tencent.com, will@kernel.org,
x86@kernel.org
Subject: Re: [syzbot] inconsistent lock state in sync_info_debugfs_show
Date: Sun, 20 Nov 2022 12:51:19 -0800 [thread overview]
Message-ID: <000000000000cbce8405eded1951@google.com> (raw)
In-Reply-To: <00000000000021719805d692e035@google.com>
syzbot has bisected this issue to:
commit 997acaf6b4b59c6a9c259740312a69ea549cc684
Author: Mark Rutland <mark.rutland@arm.com>
Date: Mon Jan 11 15:37:07 2021 +0000
lockdep: report broken irq restoration
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=115b350d880000
start commit: 84368d882b96 Merge tag 'soc-fixes-6.1-3' of git://git.kern..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=135b350d880000
console output: https://syzkaller.appspot.com/x/log.txt?x=155b350d880000
kernel config: https://syzkaller.appspot.com/x/.config?x=6f4e5e9899396248
dashboard link: https://syzkaller.appspot.com/bug?extid=007bfe0f3330f6e1e7d1
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=164376f9880000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=16cf0965880000
Reported-by: syzbot+007bfe0f3330f6e1e7d1@syzkaller.appspotmail.com
Fixes: 997acaf6b4b5 ("lockdep: report broken irq restoration")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2022-11-20 20:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-27 16:33 [syzbot] inconsistent lock state in sync_info_debugfs_show syzbot
2022-11-19 2:46 ` syzbot
2022-11-22 14:51 ` Daniel Vetter
2022-11-22 14:51 ` Daniel Vetter
2022-11-22 17:31 ` Christian König
2022-11-20 20:51 ` syzbot [this message]
2022-11-22 19:48 ` Daniel Vetter
2022-11-22 19:48 ` Daniel Vetter
[not found] <20221119081011.4372-1-hdanton@sina.com>
2022-11-19 9:43 ` syzbot
[not found] <20221119095108.4564-1-hdanton@sina.com>
2022-11-19 10:50 ` 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=000000000000cbce8405eded1951@google.com \
--to=syzbot+007bfe0f3330f6e1e7d1@syzkaller.appspotmail.com \
--cc=bp@alien8.de \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=gustavo@padovan.org \
--cc=hdanton@sina.com \
--cc=hpa@zytor.com \
--cc=jmattson@google.com \
--cc=joro@8bytes.org \
--cc=kvm@vger.kernel.org \
--cc=linaro-mm-sig-bounces@lists.linaro.org \
--cc=linaro-mm-sig@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peterz@infradead.org \
--cc=seanjc@google.com \
--cc=sumit.semwal@linaro.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
--cc=vkuznets@redhat.com \
--cc=wanpengli@tencent.com \
--cc=will@kernel.org \
--cc=x86@kernel.org \
/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.