netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Schmidt <stefan@datenfreihafen.org>
To: davem@davemloft.net, kuba@kernel.org
Cc: linux-wpan@vger.kernel.org, alex.aring@gmail.com, netdev@vger.kernel.org
Subject: pull-request: ieee802154 for net 2021-04-07
Date: Wed,  7 Apr 2021 16:55:05 +0200	[thread overview]
Message-ID: <20210407145505.467867-1-stefan@datenfreihafen.org> (raw)

Hello Dave, Jakub.

An update from ieee802154 for your *net* tree.

Most of these are coming from the flood of syzkaller reports
lately got for the ieee802154 subsystem. There are likely to
come more for this, but this is a good batch to get out for now.

Alexander Aring created a patchset to avoid llsec handling on a
monitor interface, which we do not support.
Alex Shi removed a unused macro.
Pavel Skripkin fixed another protection fault found by syzkaller.

regards
Stefan Schmidt

The following changes since commit fcb3007371e1a4afb03280af1b336a83287fe115:

  Merge branch 'wireguard-fixes-for-5-12-rc1' (2021-02-23 15:59:35 -0800)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/sschmidt/wpan.git tags/ieee802154-for-davem-2021-04-07

for you to fetch changes up to 1165affd484889d4986cf3b724318935a0b120d8:

  net: mac802154: Fix general protection fault (2021-04-06 22:42:16 +0200)

----------------------------------------------------------------
Alex Shi (1):
      net/ieee802154: remove unused macros to tame gcc

Alexander Aring (19):
      net: ieee802154: fix nl802154 del llsec key
      net: ieee802154: fix nl802154 del llsec dev
      net: ieee802154: fix nl802154 add llsec key
      net: ieee802154: fix nl802154 del llsec devkey
      net: ieee802154: nl-mac: fix check on panid
      net: ieee802154: forbid monitor for set llsec params
      net: ieee802154: stop dump llsec keys for monitors
      net: ieee802154: forbid monitor for add llsec key
      net: ieee802154: forbid monitor for del llsec key
      net: ieee802154: stop dump llsec devs for monitors
      net: ieee802154: forbid monitor for add llsec dev
      net: ieee802154: forbid monitor for del llsec dev
      net: ieee802154: stop dump llsec devkeys for monitors
      net: ieee802154: forbid monitor for add llsec devkey
      net: ieee802154: forbid monitor for del llsec devkey
      net: ieee802154: stop dump llsec seclevels for monitors
      net: ieee802154: forbid monitor for add llsec seclevel
      net: ieee802154: forbid monitor for del llsec seclevel
      net: ieee802154: stop dump llsec params for monitors

Pavel Skripkin (1):
      net: mac802154: Fix general protection fault

Stefan Schmidt (1):
      Merge remote-tracking branch 'net/master'

 net/ieee802154/nl-mac.c   |  7 ++---
 net/ieee802154/nl802154.c | 68 +++++++++++++++++++++++++++++++++++++++++------
 net/mac802154/llsec.c     |  2 +-
 3 files changed, 65 insertions(+), 12 deletions(-)

             reply	other threads:[~2021-04-07 14:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-07 14:55 Stefan Schmidt [this message]
2021-04-07 22:20 ` pull-request: ieee802154 for net 2021-04-07 patchwork-bot+netdevbpf

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=20210407145505.467867-1-stefan@datenfreihafen.org \
    --to=stefan@datenfreihafen.org \
    --cc=alex.aring@gmail.com \
    --cc=davem@davemloft.net \
    --cc=kuba@kernel.org \
    --cc=linux-wpan@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    /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 NNTP newsgroup(s).