From: Stefan Schmidt <stefan@datenfreihafen.org>
To: davem@davemloft.net
Cc: linux-wpan@vger.kernel.org, alex.aring@gmail.com, netdev@vger.kernel.org
Subject: pull-request: ieee802154 for net 2019-09-28
Date: Sat, 28 Sep 2019 09:57:37 +0200 [thread overview]
Message-ID: <20190928075737.28132-1-stefan@datenfreihafen.org> (raw)
Hello Dave.
An update from ieee802154 for your *net* tree.
Three driver fixes. Navid Emamdoost fixed a memory leak on an error
path in the ca8210 driver, Johan Hovold fixed a use-after-free found
by syzbot in the atusb driver and Christophe JAILLET makes sure
__skb_put_data is used instead of memcpy in the mcr20a driver
I switched from branches to tags here to be pulled from. So far not
annotated and not signed. Once I fixed my scripts it should contain
this messages as annotations. If you want it signed as well just tell
me. If there are any problems let me know.
regards
Stefan Schmidt
The following changes since commit f53a7ad189594a112167efaf17ea8d0242b5ac00:
r8152: Set memory to all 0xFFs on failed reg reads (2019-08-25 19:52:59 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/sschmidt/wpan.git tags/ieee802154-for-davem-2019-09-28
for you to fetch changes up to 6402939ec86eaf226c8b8ae00ed983936b164908:
ieee802154: ca8210: prevent memory leak (2019-09-27 21:57:42 +0200)
----------------------------------------------------------------
Christophe JAILLET (1):
ieee802154: mcr20a: simplify a bit 'mcr20a_handle_rx_read_buf_complete()'
Johan Hovold (1):
ieee802154: atusb: fix use-after-free at disconnect
Navid Emamdoost (1):
ieee802154: ca8210: prevent memory leak
drivers/net/ieee802154/atusb.c | 3 ++-
drivers/net/ieee802154/ca8210.c | 2 +-
drivers/net/ieee802154/mcr20a.c | 2 +-
3 files changed, 4 insertions(+), 3 deletions(-)
next reply other threads:[~2019-09-28 7:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-28 7:57 Stefan Schmidt [this message]
2019-10-01 0:15 ` pull-request: ieee802154 for net 2019-09-28 David Miller
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=20190928075737.28132-1-stefan@datenfreihafen.org \
--to=stefan@datenfreihafen.org \
--cc=alex.aring@gmail.com \
--cc=davem@davemloft.net \
--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).