From: syzbot <syzbot+84936245a918e2cddb32@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, coreteam@netfilter.org,
davem@davemloft.net, fw@strlen.de, hannes@cmpxchg.org,
kadlec@blackhole.kfki.hu, kadlec@netfilter.org, kuba@kernel.org,
linux-kernel@vger.kernel.org, mhocko@suse.com,
netdev@vger.kernel.org, netfilter-devel@vger.kernel.org,
pablo@netfilter.org, syzkaller-bugs@googlegroups.com,
torvalds@linux-foundation.org, vbabka@suse.cz,
xiyou.wangcong@gmail.com
Subject: Re: INFO: task hung in htable_put
Date: Thu, 19 Mar 2020 21:42:04 -0700 [thread overview]
Message-ID: <00000000000039c12305a141e817@google.com> (raw)
In-Reply-To: <0000000000005eaea0059aa1dff6@google.com>
syzbot suspects this bug was fixed by commit:
commit 99b79c3900d4627672c85d9f344b5b0f06bc2a4d
Author: Cong Wang <xiyou.wangcong@gmail.com>
Date: Thu Feb 13 06:53:52 2020 +0000
netfilter: xt_hashlimit: unregister proc file before releasing mutex
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=17446eb1e00000
start commit: f2850dd5 Merge tag 'kbuild-fixes-v5.6' of git://git.kernel..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=735296e4dd620b10
dashboard link: https://syzkaller.appspot.com/bug?extid=84936245a918e2cddb32
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=17a96c29e00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=12fcc65ee00000
If the result looks correct, please mark the bug fixed by replying with:
#syz fix: netfilter: xt_hashlimit: unregister proc file before releasing mutex
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2020-03-20 4:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-26 21:15 INFO: task hung in htable_put syzbot
2020-03-20 4:42 ` syzbot [this message]
2020-11-11 13:29 ` 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=00000000000039c12305a141e817@google.com \
--to=syzbot+84936245a918e2cddb32@syzkaller.appspotmail.com \
--cc=akpm@linux-foundation.org \
--cc=coreteam@netfilter.org \
--cc=davem@davemloft.net \
--cc=fw@strlen.de \
--cc=hannes@cmpxchg.org \
--cc=kadlec@blackhole.kfki.hu \
--cc=kadlec@netfilter.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhocko@suse.com \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=torvalds@linux-foundation.org \
--cc=vbabka@suse.cz \
--cc=xiyou.wangcong@gmail.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 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).