From: syzbot <syzbot+8e467b009209f1fcf666@syzkaller.appspotmail.com>
To: andrii@kernel.org, ast@kernel.org, bpf@vger.kernel.org,
daniel@iogearbox.net, dave@pr1mo.net, davem@davemloft.net,
dsahern@kernel.org, john.fastabend@gmail.com, kafai@fb.com,
kpsingh@kernel.org, kuba@kernel.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
pabeni@redhat.com, songliubraving@fb.com,
syzkaller-bugs@googlegroups.com, yhs@fb.com,
yoshfuji@linux-ipv6.org
Subject: Re: [syzbot] possible deadlock in __sock_release
Date: Thu, 05 Aug 2021 03:13:10 -0700 [thread overview]
Message-ID: <000000000000842d2f05c8cd2ac7@google.com> (raw)
In-Reply-To: <00000000000040b7ba05ae32a94a@google.com>
syzbot suspects this issue was fixed by commit:
commit 8fb4792f091e608a0a1d353dfdf07ef55a719db5
Author: Paolo Abeni <pabeni@redhat.com>
Date: Tue Jul 20 13:08:40 2021 +0000
ipv6: fix another slab-out-of-bounds in fib6_nh_flush_exceptions
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=113a99f1300000
start commit: c6c205ed442e Merge branch 'stmmac-ptp'
git tree: net
kernel config: https://syzkaller.appspot.com/x/.config?x=26b64b13fcecb7e1
dashboard link: https://syzkaller.appspot.com/bug?extid=8e467b009209f1fcf666
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=152188d2300000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=10d5493c300000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: ipv6: fix another slab-out-of-bounds in fib6_nh_flush_exceptions
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2021-08-05 10:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-31 20:58 possible deadlock in __sock_release syzbot
2021-08-05 10:13 ` 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=000000000000842d2f05c8cd2ac7@google.com \
--to=syzbot+8e467b009209f1fcf666@syzkaller.appspotmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=dave@pr1mo.net \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=john.fastabend@gmail.com \
--cc=kafai@fb.com \
--cc=kpsingh@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=songliubraving@fb.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=yhs@fb.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.