From: Kalle Valo <kvalo@codeaurora.org>
To: Chris Rorvick <chris@rorvick.com>
Cc: linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org,
Johannes Berg <johannes.berg@intel.com>,
Emmanuel Grumbach <emmanuel.grumbach@intel.com>,
Luca Coelho <luciano.coelho@intel.com>,
Intel Linux Wireless <linuxwifi@intel.com>,
"David S. Miller" <davem@davemloft.net>
Subject: Re: [PATCH] iwlwifi: actually check allocated conf_tlv pointer
Date: Sun, 05 Apr 2020 11:44:53 +0300 [thread overview]
Message-ID: <87mu7qfhiy.fsf@codeaurora.org> (raw)
In-Reply-To: <20200402050219.4842-1-chris@rorvick.com> (Chris Rorvick's message of "Thu, 2 Apr 2020 00:02:19 -0500")
Chris Rorvick <chris@rorvick.com> writes:
> Commit 71bc0334a637 ("iwlwifi: check allocated pointer when allocating
> conf_tlvs") attempted to fix a typoe introduced by commit 17b809c9b22e
> ("iwlwifi: dbg: move debug data to a struct") but does not implement the
> check correctly.
>
> Tweeted-by: @grsecurity
> Signed-off-by: Chris Rorvick <chris@rorvick.com>
I'll add:
Fixes: 71bc0334a637 ("iwlwifi: check allocated pointer when allocating conf_tlvs")
> ---
> In this wasn't picked up?
Luca, can I take this directly?
--
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2020-04-05 8:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-02 5:02 [PATCH] iwlwifi: actually check allocated conf_tlv pointer Chris Rorvick
2020-04-05 8:44 ` Kalle Valo [this message]
2020-04-05 8:51 ` Luca Coelho
2020-04-05 9:13 ` Kalle Valo
2020-04-14 12:14 ` Sedat Dilek
2020-04-06 14:10 ` Kalle Valo
2020-04-06 19:53 ` Sedat Dilek
2020-04-08 9:07 ` Sedat Dilek
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=87mu7qfhiy.fsf@codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=chris@rorvick.com \
--cc=davem@davemloft.net \
--cc=emmanuel.grumbach@intel.com \
--cc=johannes.berg@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linuxwifi@intel.com \
--cc=luciano.coelho@intel.com \
--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).