All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+d4336c84ed0099fdbe47@syzkaller.appspotmail.com>
To: keescook@chromium.org, linux-kernel@vger.kernel.org,
	mingo@kernel.org, mingo@redhat.com, peterz@infradead.org,
	syzkaller-bugs@googlegroups.com, tglx@linutronix.de,
	will@kernel.org
Subject: Re: WARNING in irqentry_exit
Date: Wed, 11 Nov 2020 18:01:07 -0800	[thread overview]
Message-ID: <00000000000005858405b3df4904@google.com> (raw)
In-Reply-To: <000000000000e3068105ac405407@google.com>

syzbot suspects this issue was fixed by commit:

commit 4d004099a668c41522242aa146a38cc4eb59cb1e
Author: Peter Zijlstra <peterz@infradead.org>
Date:   Fri Oct 2 09:04:21 2020 +0000

    lockdep: Fix lockdep recursion

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=1202919a500000
start commit:   f873db9a Merge tag 'io_uring-5.9-2020-08-21' of git://git...
git tree:       upstream
kernel config:  https://syzkaller.appspot.com/x/.config?x=a0437fdd630bee11
dashboard link: https://syzkaller.appspot.com/bug?extid=d4336c84ed0099fdbe47
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=15312a66900000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=13b01641900000

If the result looks correct, please mark the issue as fixed by replying with:

#syz fix: lockdep: Fix lockdep recursion

For information about bisection process see: https://goo.gl/tpsmEJ#bisection

  reply	other threads:[~2020-11-12  5:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-07  2:26 WARNING in irqentry_exit syzbot
2020-11-12  2:01 ` syzbot [this message]
2020-11-12  9:37   ` 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=00000000000005858405b3df4904@google.com \
    --to=syzbot+d4336c84ed0099fdbe47@syzkaller.appspotmail.com \
    --cc=keescook@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=tglx@linutronix.de \
    --cc=will@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.