[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <00000000000089c74405a84be7aa@google.com>
Date: Wed, 17 Jun 2020 11:34:04 -0700
From: syzbot <syzbot+6174a6c5eba4b3cdd606@...kaller.appspotmail.com>
To: agruenba@...hat.com, bp@...en8.de, cluster-devel@...hat.com,
davem@...emloft.net, hpa@...or.com, jon.maloy@...csson.com,
keescook@...omium.org, konrad.wilk@...cle.com,
kuznet@....inr.ac.ru, len.brown@...el.com,
linux-kernel@...r.kernel.org, luto@...capital.net,
mingo@...hat.com, netdev@...r.kernel.org, nstange@...e.de,
puwen@...on.cn, rpeterso@...hat.com,
syzkaller-bugs@...glegroups.com, tglx@...utronix.de,
tipc-discussion@...ts.sourceforge.net, wad@...omium.org,
wang.yi59@....com.cn, x86@...nel.org, ying.xue@...driver.com,
yoshfuji@...ux-ipv6.org
Subject: Re: WARNING: locking bug in __queue_work
syzbot suspects this bug was fixed by commit:
commit ea22eee4e6027d8927099de344f7fff43c507ef9
Author: Bob Peterson <rpeterso@...hat.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
Powered by blists - more mailing lists