From: Kalle Valo <kvalo@codeaurora.org>
To: Lorenzo Bianconi <lorenzo.bianconi@redhat.com>
Cc: linux-wireless@vger.kernel.org, nbd@nbd.name,
sgruszka@redhat.com, stefan.wahren@i2se.com
Subject: Re: [PATCH wireless-drivers 0/3] fix multiple issues in mt76u error path
Date: Tue, 12 Feb 2019 20:59:40 +0200 [thread overview]
Message-ID: <87va1orfxf.fsf@purkki.adurom.net> (raw)
In-Reply-To: <cover.1549832428.git.lorenzo.bianconi@redhat.com> (Lorenzo Bianconi's message of "Sun, 10 Feb 2019 22:49:12 +0100")
Lorenzo Bianconi <lorenzo.bianconi@redhat.com> writes:
> Fix following issues in mt76u initialization error path:
> - NULL pointer dereference in mt76u_mcu_deinit
> - possible memory leak in mt76u_buf_free
> - use-after-free warning since mt76u_queues_deinit is run twice
>
> This series has been tested running mt76x0u driver on rpi3+
> (dwc_otg controller does not support SG I/O)
>
> Lorenzo Bianconi (3):
> mt76: usb: fix possible NULL pointer dereference in mt76u_mcu_deinit
> mt76: usb: fix possible memory leak in mt76u_buf_free
> mt76: usb: do not run mt76u_queues_deinit twice
As we are in -rc6 now, better to push these via -next. So I assume Felix
will take these.
--
Kalle Valo
next prev parent reply other threads:[~2019-02-12 18:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-10 21:49 [PATCH wireless-drivers 0/3] fix multiple issues in mt76u error path Lorenzo Bianconi
2019-02-10 21:49 ` [PATCH wireless-drivers 1/3] mt76: usb: fix possible NULL pointer dereference in mt76u_mcu_deinit Lorenzo Bianconi
2019-02-10 21:49 ` [PATCH wireless-drivers 2/3] mt76: usb: fix possible memory leak in mt76u_buf_free Lorenzo Bianconi
2019-02-10 21:49 ` [PATCH wireless-drivers 3/3] mt76: usb: do not run mt76u_queues_deinit twice Lorenzo Bianconi
2019-02-12 18:59 ` Kalle Valo [this message]
2019-02-18 18:56 ` [PATCH wireless-drivers 0/3] fix multiple issues in mt76u error path Felix Fietkau
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=87va1orfxf.fsf@purkki.adurom.net \
--to=kvalo@codeaurora.org \
--cc=linux-wireless@vger.kernel.org \
--cc=lorenzo.bianconi@redhat.com \
--cc=nbd@nbd.name \
--cc=sgruszka@redhat.com \
--cc=stefan.wahren@i2se.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 NNTP newsgroup(s).