From: Dmitry Vyukov <dvyukov@google.com>
To: syzbot <syzbot+84936245a918e2cddb32@syzkaller.appspotmail.com>,
syzkaller-bugs <syzkaller-bugs@googlegroups.com>,
netdev <netdev@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
coreteam@netfilter.org
Subject: Re: INFO: task hung in htable_put
Date: Wed, 11 Nov 2020 14:29:57 +0100 [thread overview]
Message-ID: <CACT4Y+YFEhTsTdjNTpkcrmDdWJriS-ezgxM_q9U2enepcoFTQQ@mail.gmail.com> (raw)
In-Reply-To: <00000000000039c12305a141e817@google.com>
On Fri, Mar 20, 2020 at 5:42 AM syzbot
<syzbot+84936245a918e2cddb32@syzkaller.appspotmail.com> wrote:
>
> 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
#syz fix: netfilter: xt_hashlimit: unregister proc file before releasing mutex
prev parent reply other threads:[~2020-11-11 13:30 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
2020-11-11 13:29 ` Dmitry Vyukov [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=CACT4Y+YFEhTsTdjNTpkcrmDdWJriS-ezgxM_q9U2enepcoFTQQ@mail.gmail.com \
--to=dvyukov@google.com \
--cc=coreteam@netfilter.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=syzbot+84936245a918e2cddb32@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.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).