From: Sasha Levin <sashal@kernel.org>
To: Sasha Levin <sashal@kernel.org>
To: Felix Fietkau <nbd@nbd.name>
To: linux-wireless@vger.kernel.org
Cc: kvalo@codeaurora.org, stable@vger.kernel.org
Cc: stable@vger.kernel.org
Cc: stable@vger.kernel.org
Subject: Re: [PATCH 5.6] mt76: fix array overflow on receiving too many fragments for a packet
Date: Sat, 22 Feb 2020 14:13:53 +0000 [thread overview]
Message-ID: <20200222141354.EFA18206D7@mail.kernel.org> (raw)
In-Reply-To: <20200220114139.46508-1-nbd@nbd.name>
Hi,
[This is an automated email]
This commit has been processed because it contains a -stable tag.
The stable tag indicates that it's relevant for the following trees: all
The bot has tested the following trees: v5.5.5, v5.4.21, v4.19.105, v4.14.171, v4.9.214, v4.4.214.
v5.5.5: Build OK!
v5.4.21: Build OK!
v4.19.105: Build OK!
v4.14.171: Failed to apply! Possible dependencies:
17f1de56df05 ("mt76: add common code shared between multiple chipsets")
v4.9.214: Failed to apply! Possible dependencies:
17f1de56df05 ("mt76: add common code shared between multiple chipsets")
v4.4.214: Failed to apply! Possible dependencies:
17f1de56df05 ("mt76: add common code shared between multiple chipsets")
NOTE: The patch will not be queued to stable trees until it is upstream.
How should we proceed with this patch?
--
Thanks,
Sasha
next prev parent reply other threads:[~2020-02-22 14:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-20 11:41 [PATCH 5.6] mt76: fix array overflow on receiving too many fragments for a packet Felix Fietkau
2020-02-22 14:13 ` Sasha Levin [this message]
2020-03-03 15:30 ` Kalle Valo
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=20200222141354.EFA18206D7@mail.kernel.org \
--to=sashal@kernel.org \
--cc=kvalo@codeaurora.org \
--cc=stable@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).