mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Igor Mitsyanko <igor.mitsyanko.os@quantenna.com>
To: Colin King <colin.king@canonical.com>,
	Avinash Patil <avinashp@quantenna.com>,
	Sergey Matyukevich <smatyukevich@quantenna.com>,
	Kalle Valo <kvalo@codeaurora.org>,
	Dmitrii Lebed <dlebed@quantenna.com>,
	Huizhao Wang <hwang@quantenna.com>,
	linux-wireless@vger.kernel.org, netdev@vger.kernel.org
Cc: kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH][wireless-next] qtnfmac: check band before allocating cmd_skb to avoid resource leak
Date: Fri, 2 Jun 2017 10:32:42 -0700	[thread overview]
Message-ID: <47b42ab3-ae0d-688b-7024-0f70e0606902@quantenna.com> (raw)
In-Reply-To: <20170602154045.28948-1-colin.king@canonical.com>

On 06/02/2017 08:40 AM, Colin King wrote:
> External Email
>
>
> From: Colin Ian King <colin.king@canonical.com>
>
> The current code allocates cmd_skb and then will leak this if band->band
> is an illegal value. It is simpler to sanity check the band first before
> allocating cmd_skb so that we don't have to free cmd_skb if an invalid
> band occurs.
>
> Detected by CoverityScan, CID#1437561 ("Resource Leak")
>
> Signed-off-by: Colin Ian King <colin.king@canonical.com>
> ---
>   drivers/net/wireless/quantenna/qtnfmac/commands.c | 12 ++++++------
>   1 file changed, 6 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/net/wireless/quantenna/qtnfmac/commands.c b/drivers/net/wireless/quantenna/qtnfmac/commands.c
> index f0a0cfa7d8a1..cce62f39edaf 100644
> --- a/drivers/net/wireless/quantenna/qtnfmac/commands.c
> +++ b/drivers/net/wireless/quantenna/qtnfmac/commands.c
> @@ -1300,12 +1300,6 @@ int qtnf_cmd_get_mac_chan_info(struct qtnf_wmac *mac,
>          int ret = 0;
>          u8 qband;
>
> -       cmd_skb = qtnf_cmd_alloc_new_cmdskb(mac->macid, 0,
> -                                           QLINK_CMD_CHANS_INFO_GET,
> -                                           sizeof(*cmd));
> -       if (!cmd_skb)
> -               return -ENOMEM;
> -
>          switch (band->band) {
>          case NL80211_BAND_2GHZ:
>                  qband = QLINK_BAND_2GHZ;
> @@ -1320,6 +1314,12 @@ int qtnf_cmd_get_mac_chan_info(struct qtnf_wmac *mac,
>                  return -EINVAL;
>          }
>
> +       cmd_skb = qtnf_cmd_alloc_new_cmdskb(mac->macid, 0,
> +                                           QLINK_CMD_CHANS_INFO_GET,
> +                                           sizeof(*cmd));
> +       if (!cmd_skb)
> +               return -ENOMEM;
> +
>          cmd = (struct qlink_cmd_chans_info_get *)cmd_skb->data;
>          cmd->band = qband;
>          ret = qtnf_cmd_send_with_reply(mac->bus, cmd_skb, &resp_skb, &res_code,
> --
> 2.11.0
>
Reviewed-by: Igor Mitsyanko <igor.mitsyanko.os@quantenna.com>

  reply	other threads:[~2017-06-02 17:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-02 15:40 Colin King
2017-06-02 17:32 ` Igor Mitsyanko [this message]
2017-06-13  7:02 ` [wireless-next] " 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=47b42ab3-ae0d-688b-7024-0f70e0606902@quantenna.com \
    --to=igor.mitsyanko.os@quantenna.com \
    --cc=avinashp@quantenna.com \
    --cc=colin.king@canonical.com \
    --cc=dlebed@quantenna.com \
    --cc=hwang@quantenna.com \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=kvalo@codeaurora.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=smatyukevich@quantenna.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

all inboxes | Powered by JetHome®