From: syzbot <syzbot+a41dfef1d2e04910eb2e@syzkaller.appspotmail.com>
To: a@unstable.cc, b.a.t.m.a.n@lists.open-mesh.org,
davem@davemloft.net, hdanton@sina.com, johan.hedberg@gmail.com,
kuba@kernel.org, linux-bluetooth@vger.kernel.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
luiz.dentz@gmail.com, marcel@holtmann.org,
mareklindner@neomailbox.ch, miklos@szeredi.hu,
mszeredi@redhat.com, netdev@vger.kernel.org,
sw@simonwunderlich.de, syzkaller-bugs@googlegroups.com
Subject: Re: INFO: trying to register non-static key in l2cap_sock_teardown_cb
Date: Sun, 10 Jan 2021 21:16:06 -0800 [thread overview]
Message-ID: <000000000000cbca0705b89900b3@google.com> (raw)
In-Reply-To: <000000000000f5964705b7d47d8c@google.com>
syzbot has bisected this issue to:
commit 4680a7ee5db27772af40d83393fa0fb955b745b7
Author: Miklos Szeredi <mszeredi@redhat.com>
Date: Sat Oct 1 05:32:33 2016 +0000
fuse: remove duplicate cs->offset assignment
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=11fc80e7500000
start commit: 73b7a604 net: dsa: bcm_sf2: support BCM4908's integrated s..
git tree: net-next
final oops: https://syzkaller.appspot.com/x/report.txt?x=13fc80e7500000
console output: https://syzkaller.appspot.com/x/log.txt?x=15fc80e7500000
kernel config: https://syzkaller.appspot.com/x/.config?x=9ce34124da4c882b
dashboard link: https://syzkaller.appspot.com/bug?extid=a41dfef1d2e04910eb2e
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=166ee4cf500000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1337172f500000
Reported-by: syzbot+a41dfef1d2e04910eb2e@syzkaller.appspotmail.com
Fixes: 4680a7ee5db2 ("fuse: remove duplicate cs->offset assignment")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2021-01-11 5:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-01 10:49 INFO: trying to register non-static key in l2cap_sock_teardown_cb syzbot
2021-01-10 21:40 ` syzbot
2021-01-11 5:16 ` syzbot [this message]
2021-11-30 16:19 ` [syzbot] " syzbot
2021-12-04 9:32 ` Dmitry Vyukov
2021-12-04 9:32 ` 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=000000000000cbca0705b89900b3@google.com \
--to=syzbot+a41dfef1d2e04910eb2e@syzkaller.appspotmail.com \
--cc=a@unstable.cc \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
--cc=davem@davemloft.net \
--cc=hdanton@sina.com \
--cc=johan.hedberg@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=mareklindner@neomailbox.ch \
--cc=miklos@szeredi.hu \
--cc=mszeredi@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=sw@simonwunderlich.de \
--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 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.