From: Linus Torvalds <firstname.lastname@example.org>
To: Johannes Berg <email@example.com>
Cc: Arend van Spriel <firstname.lastname@example.org>,
Kalle Valo <email@example.com>,
Linux Wireless List <firstname.lastname@example.org>
Subject: Re: [PATCH] brcmfmac: fix possible buffer overflow in brcmf_cfg80211_mgmt_tx()
Date: Fri, 7 Jul 2017 09:37:08 -0700 [thread overview]
Message-ID: <CA+55aFzV_Gp=q7r+WjNV9epaCaAFqirXfMVD1=+CcfwGV1SGoA@mail.gmail.com> (raw)
On Fri, Jul 7, 2017 at 6:17 AM, Johannes Berg <email@example.com> wrote:
> Linus, since you were involved already, will you apply this directly?
I don't think it's _that_ urgent, since it's specific to one
particular driver anyway. I'd suggest just going through the normal
channels, and be cc'd to netdev.
> I guess it should also have a Cc: stable tag, and perhaps a Fixes?
The fixes tag would be
Fixes: 18e2f61db3b70 ("brcmfmac: P2P action frame tx.")
which is 3.9 in case anybody cares. I assume that didn't get
backported any further.
prev parent reply other threads:[~2017-07-07 16:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-07 12:01 [PATCH] brcmfmac: fix possible buffer overflow in brcmf_cfg80211_mgmt_tx() Arend van Spriel
2017-07-07 12:47 ` Sedat Dilek
2017-07-07 19:39 ` Arend van Spriel
2017-07-12 9:59 ` Sedat Dilek
2017-07-07 13:17 ` Johannes Berg
2017-07-07 16:37 ` Linus Torvalds [this message]
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).