From: Simon Horman <simon.horman@corigine.com>
To: Aleksandr Nogikh <nogikh@google.com>
Cc: Miquel Raynal <miquel.raynal@bootlin.com>,
syzbot <syzbot+bd85b31816913a32e473@syzkaller.appspotmail.com>,
alex.aring@gmail.com, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, linux-kernel@vger.kernel.org,
linux-wpan@vger.kernel.org, netdev@vger.kernel.org,
pabeni@redhat.com, stefan@datenfreihafen.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [wpan?] general protection fault in nl802154_trigger_scan
Date: Wed, 8 Mar 2023 10:38:42 +0100 [thread overview]
Message-ID: <ZAhXoqIIDSn+MzDL@corigine.com> (raw)
In-Reply-To: <CANp29Y6aaCVVg+3ezNzaw1nqvMbZhHooZ_DQRvv5YPbOmeprag@mail.gmail.com>
On Tue, Mar 07, 2023 at 07:40:13PM +0100, Aleksandr Nogikh wrote:
> [You don't often get email from nogikh@google.com. Learn why this is important at https://aka.ms/LearnAboutSenderIdentification ]
>
> On Sat, Mar 4, 2023 at 9:16 AM 'Miquel Raynal' via syzkaller-bugs
> <syzkaller-bugs@googlegroups.com> wrote:
> >
> > > I believe this is fixed here:
> > >
> > > - [PATCH net] ieee802154: Prevent user from crashing the host
> > > https://lore.kernel.org/netdev/20230301154450.547716-1-miquel.raynal@bootlin.com/
> > >
> > > - pull-request: ieee802154 for net 2023-03-02
> > > https://lore.kernel.org/netdev/20230302153032.1312755-1-stefan@datenfreihafen.org/
> >
> > Hopefully, yes :)
> >
> > Thanks,
> > Miquèl
>
> Let's tell syzbot about the fix:
>
> #syz fix: ieee802154: Prevent user from crashing the host
Thanks, I was wondering about that.
prev parent reply other threads:[~2023-03-08 9:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-03 14:30 [syzbot] [wpan?] general protection fault in nl802154_trigger_scan syzbot
2023-03-03 15:28 ` Simon Horman
2023-03-03 15:44 ` Miquel Raynal
2023-03-07 18:40 ` Aleksandr Nogikh
2023-03-08 9:38 ` Simon Horman [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=ZAhXoqIIDSn+MzDL@corigine.com \
--to=simon.horman@corigine.com \
--cc=alex.aring@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wpan@vger.kernel.org \
--cc=miquel.raynal@bootlin.com \
--cc=netdev@vger.kernel.org \
--cc=nogikh@google.com \
--cc=pabeni@redhat.com \
--cc=stefan@datenfreihafen.org \
--cc=syzbot+bd85b31816913a32e473@syzkaller.appspotmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).