From: syzbot <syzbot+cde43a581a8e5f317bc2@syzkaller.appspotmail.com>
To: alex.aring@gmail.com, davem@davemloft.net, kuba@kernel.org,
linux-kernel@vger.kernel.org, linux-wpan@vger.kernel.org,
netdev@vger.kernel.org, stefan@datenfreihafen.org,
syzkaller-bugs@googlegroups.com
Subject: Re: WARNING in ieee802154_get_llsec_params
Date: Thu, 04 Mar 2021 22:37:04 -0800 [thread overview]
Message-ID: <000000000000f70f8f05bcc44f14@google.com> (raw)
In-Reply-To: <0000000000009b387305bc00fda6@google.com>
syzbot has bisected this issue to:
commit b60673c4c418bef7550d02faf53c34fbfeb366bf
Author: Jakub Kicinski <kuba@kernel.org>
Date: Tue Mar 3 05:05:15 2020 +0000
nl802154: add missing attribute validation for dev_type
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=100b11b0d00000
start commit: f5427c24 Add linux-next specific files for 20210304
git tree: linux-next
final oops: https://syzkaller.appspot.com/x/report.txt?x=120b11b0d00000
console output: https://syzkaller.appspot.com/x/log.txt?x=140b11b0d00000
kernel config: https://syzkaller.appspot.com/x/.config?x=a7876f68bf0bea99
dashboard link: https://syzkaller.appspot.com/bug?extid=cde43a581a8e5f317bc2
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=124c7b46d00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1276f5b0d00000
Reported-by: syzbot+cde43a581a8e5f317bc2@syzkaller.appspotmail.com
Fixes: b60673c4c418 ("nl802154: add missing attribute validation for dev_type")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2021-03-05 6:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-23 13:35 WARNING in ieee802154_get_llsec_params syzbot
2021-03-05 0:04 ` syzbot
2021-03-05 6:37 ` 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=000000000000f70f8f05bcc44f14@google.com \
--to=syzbot+cde43a581a8e5f317bc2@syzkaller.appspotmail.com \
--cc=alex.aring@gmail.com \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wpan@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=stefan@datenfreihafen.org \
--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.