All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@kernel.org>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: linux-wireless@vger.kernel.org,  linux-kernel@vger.kernel.org,
	 kernel test robot <lkp@intel.com>,
	 Dan Carpenter <dan.carpenter@linaro.org>
Subject: Re: [PATCH] wifi: cw1200: Fix potential NULL dereference
Date: Tue, 17 Dec 2024 16:31:31 +0200	[thread overview]
Message-ID: <87jzbymldo.fsf@kernel.org> (raw)
In-Reply-To: <20241217-cw1200-fix-v1-1-911e6b5823ec@linaro.org> (Linus Walleij's message of "Tue, 17 Dec 2024 13:55:48 +0100")

Linus Walleij <linus.walleij@linaro.org> writes:

> A recent refactoring was identified by static analysis to
> cause another potential NULL dereference, fix this!
>
> Reported-by: kernel test robot <lkp@intel.com>
> Reported-by: Dan Carpenter <dan.carpenter@linaro.org>
> Closes: https://lore.kernel.org/r/202411271742.Xa7CNVh1-lkp@intel.com/
> Fixes: 2719a9e7156c ("wifi: cw1200: Convert to GPIO descriptors")
> Signed-off-by: Linus Walleij <linus.walleij@linaro.org>

If it's ok for you, I'll add the smatch warning to the commit message:

drivers/net/wireless/st/cw1200/cw1200_spi.c:440 cw1200_spi_disconnect() error: we previously assumed 'self' could be null (see line 433)


-- 
https://patchwork.kernel.org/project/linux-wireless/list/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches

  reply	other threads:[~2024-12-17 14:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-17 12:55 [PATCH] wifi: cw1200: Fix potential NULL dereference Linus Walleij
2024-12-17 14:31 ` Kalle Valo [this message]
2024-12-17 14:49   ` Linus Walleij
2024-12-18 17:58 ` Kalle Valo
  -- strict thread matches above, loose matches on Subject: below --
2024-10-28 22:06 [PATCH] " Linus Walleij
2024-10-31 14:20 ` 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=87jzbymldo.fsf@kernel.org \
    --to=kvalo@kernel.org \
    --cc=dan.carpenter@linaro.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=lkp@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.