From: syzbot <syzbot+6174a6c5eba4b3cdd606@syzkaller.appspotmail.com>
To: agruenba@redhat.com, bp@alien8.de, cluster-devel@redhat.com,
davem@davemloft.net, hpa@zytor.com, jon.maloy@ericsson.com,
keescook@chromium.org, konrad.wilk@oracle.com,
kuznet@ms2.inr.ac.ru, len.brown@intel.com,
linux-kernel@vger.kernel.org, luto@amacapital.net,
mingo@redhat.com, netdev@vger.kernel.org, nstange@suse.de,
puwen@hygon.cn, rpeterso@redhat.com,
syzkaller-bugs@googlegroups.com, tglx@linutronix.de,
tipc-discussion@lists.sourceforge.net, wad@chromium.org,
wang.yi59@zte.com.cn, x86@kernel.org, ying.xue@windriver.com,
yoshfuji@linux-ipv6.org
Subject: Re: WARNING: locking bug in __queue_work
Date: Wed, 17 Jun 2020 11:34:04 -0700 [thread overview]
Message-ID: <00000000000089c74405a84be7aa@google.com> (raw)
In-Reply-To: <0000000000000655c0057cd141f1@google.com>
syzbot suspects this bug was fixed by commit:
commit ea22eee4e6027d8927099de344f7fff43c507ef9
Author: Bob Peterson <rpeterso@redhat.com>
Date: Wed Apr 29 13:45:54 2020 +0000
gfs2: Allow lock_nolock mount to specify jid=X
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=16fcf249100000
start commit: fe5cdef2 Merge tag 'for-linus-5.1-2' of git://github.com/c..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=856fc6d0fbbeede9
dashboard link: https://syzkaller.appspot.com/bug?extid=6174a6c5eba4b3cdd606
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=17f6c7e3200000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=101507fd200000
If the result looks correct, please mark the bug fixed by replying with:
#syz fix: gfs2: Allow lock_nolock mount to specify jid=X
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2020-06-17 18:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-12 11:11 WARNING: locking bug in __queue_work syzbot
2019-02-15 16:37 ` syzbot
2019-03-16 14:49 ` syzbot
2020-06-17 18:34 ` syzbot [this message]
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=00000000000089c74405a84be7aa@google.com \
--to=syzbot+6174a6c5eba4b3cdd606@syzkaller.appspotmail.com \
--cc=agruenba@redhat.com \
--cc=bp@alien8.de \
--cc=cluster-devel@redhat.com \
--cc=davem@davemloft.net \
--cc=hpa@zytor.com \
--cc=jon.maloy@ericsson.com \
--cc=keescook@chromium.org \
--cc=konrad.wilk@oracle.com \
--cc=kuznet@ms2.inr.ac.ru \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=mingo@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=nstange@suse.de \
--cc=puwen@hygon.cn \
--cc=rpeterso@redhat.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
--cc=tipc-discussion@lists.sourceforge.net \
--cc=wad@chromium.org \
--cc=wang.yi59@zte.com.cn \
--cc=x86@kernel.org \
--cc=ying.xue@windriver.com \
--cc=yoshfuji@linux-ipv6.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 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).