From: syzbot <syzbot+a2ec7a7fb2331091aecf@syzkaller.appspotmail.com>
To: davem@davemloft.net, dsahern@kernel.org,
johannes@sipsolutions.net, kuba@kernel.org,
linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org,
netdev@vger.kernel.org, syzkaller-bugs@googlegroups.com,
vladbu@nvidia.com, xiyou.wangcong@gmail.com,
yoshfuji@linux-ipv6.org
Subject: Re: INFO: task hung in rsvp_delete_filter_work
Date: Fri, 05 Mar 2021 02:31:04 -0800 [thread overview]
Message-ID: <000000000000d3088f05bcc7943d@google.com> (raw)
In-Reply-To: <0000000000001be3ac05ba42cef9@google.com>
syzbot suspects this issue was fixed by commit:
commit 396d7f23adf9e8c436dd81a69488b5b6a865acf8
Author: Vlad Buslov <vladbu@nvidia.com>
Date: Tue Feb 16 16:22:00 2021 +0000
net: sched: fix police ext initialization
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=13dc3caed00000
start commit: 14e8e0f6 tcp: shrink inet_connection_sock icsk_mtup enable..
git tree: net-next
kernel config: https://syzkaller.appspot.com/x/.config?x=ac6e76902c1abb76
dashboard link: https://syzkaller.appspot.com/bug?extid=a2ec7a7fb2331091aecf
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=114d33d8d00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=12610ac4d00000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: net: sched: fix police ext initialization
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2021-03-05 10:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-01 9:16 INFO: task hung in rsvp_delete_filter_work syzbot
2021-03-05 10:31 ` 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=000000000000d3088f05bcc7943d@google.com \
--to=syzbot+a2ec7a7fb2331091aecf@syzkaller.appspotmail.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=johannes@sipsolutions.net \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=vladbu@nvidia.com \
--cc=xiyou.wangcong@gmail.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 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.