From: syzbot <syzbot+7bf7b22759195c9a21e9@syzkaller.appspotmail.com>
To: aahringo@redhat.com, alex.aring@gmail.com,
anant.thazhemadam@gmail.com, davem@davemloft.net,
kuba@kernel.org, linux-kernel@vger.kernel.org,
linux-wpan@vger.kernel.org, netdev@vger.kernel.org,
paskripkin@gmail.com, stefan@datenfreihafen.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] UBSAN: shift-out-of-bounds in nl802154_new_interface
Date: Sun, 26 Dec 2021 22:09:08 -0800 [thread overview]
Message-ID: <000000000000f09fca05d41a8aee@google.com> (raw)
In-Reply-To: <000000000000e37c9805bbe843c1@google.com>
syzbot suspects this issue was fixed by commit:
commit 451dc48c806a7ce9fbec5e7a24ccf4b2c936e834
Author: Alexander Aring <aahringo@redhat.com>
Date: Fri Nov 12 03:09:16 2021 +0000
net: ieee802154: handle iftypes as u32
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1084d10db00000
start commit: ec681c53f8d2 Merge tag 'net-5.15-rc6' of git://git.kernel...
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=bab9d35f204746a7
dashboard link: https://syzkaller.appspot.com/bug?extid=7bf7b22759195c9a21e9
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=14398d94b00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=117fc40cb00000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: net: ieee802154: handle iftypes as u32
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2021-12-27 6:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-22 8:05 UBSAN: shift-out-of-bounds in nl802154_new_interface syzbot
2021-02-23 23:48 ` Jakub Kicinski
2021-02-24 0:26 ` Alexander Aring
2021-02-24 0:49 ` Jakub Kicinski
2021-02-24 13:40 ` Stefan Schmidt
2021-12-27 6:09 ` syzbot [this message]
2022-01-24 12:59 ` [syzbot] " Pavel Skripkin
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=000000000000f09fca05d41a8aee@google.com \
--to=syzbot+7bf7b22759195c9a21e9@syzkaller.appspotmail.com \
--cc=aahringo@redhat.com \
--cc=alex.aring@gmail.com \
--cc=anant.thazhemadam@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=paskripkin@gmail.com \
--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.