From: Du Cheng <ducheng2@gmail.com>
To: Alexander Aring <alex.aring@gmail.com>
Cc: Stefan Schmidt <stefan@datenfreihafen.org>,
linux-wpan - ML <linux-wpan@vger.kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
skhan@linuxfoundation.org,
syzbot+cde43a581a8e5f317bc2@syzkaller.appspotmail.com
Subject: Re: [PATCH] net:mac802154: add init of .sec and .sec_mtx for sdata in ieee802154_setup_sdata
Date: Mon, 5 Apr 2021 11:50:07 +0800 [thread overview]
Message-ID: <YGqI7w1Aj9+ilut9@nuc> (raw)
In-Reply-To: <CAB_54W5BwCoJ9u45PZrZpF49Jzh41eGvysG0KwrhoFD8e5y1Ng@mail.gmail.com>
Le Sun, Apr 04, 2021 at 08:33:48PM -0400, Alexander Aring a écrit :
> Hi,
>
> On Sun, 4 Apr 2021 at 00:57, Du Cheng <ducheng2@gmail.com> wrote:
> >
> > add mutex_init(&sdata->sec_mtx) and mac802154_llsec_init(&sdata->sec) for
> > NL802154_IFTYPE_MONITOR inside ieee802154_setup_sdata. As the unintiated
> > mutex and sec data structure were used in ieee802154_get_llsec_params
> > which would cause a kernel crash. BUG reported by syzkaller.
>
> this patch will fix it in a way that the user is allowed to set llsec
> parameters for monitors but they will never use them because it's not
> supported. I resend my patch series which should forbid monitors to
> set any llsec parameters for now and the user will be aware that this
> feature isn't supported right now.
>
> Thanks.
>
> - Alex
Hi Alex,
Noted. Please CC me when you send your patch series.
Thanks!
Regards,
Du Cheng
prev parent reply other threads:[~2021-04-05 3:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-04 4:57 [PATCH] net:mac802154: add init of .sec and .sec_mtx for sdata in ieee802154_setup_sdata Du Cheng
2021-04-05 0:33 ` Alexander Aring
2021-04-05 3:50 ` Du Cheng [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=YGqI7w1Aj9+ilut9@nuc \
--to=ducheng2@gmail.com \
--cc=alex.aring@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-wpan@vger.kernel.org \
--cc=skhan@linuxfoundation.org \
--cc=stefan@datenfreihafen.org \
--cc=syzbot+cde43a581a8e5f317bc2@syzkaller.appspotmail.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