From: Hauke Mehrtens <hauke@hauke-m.de>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: Arend van Spriel <arend@broadcom.com>, linux-wireless@vger.kernel.org
Subject: Re: brcmsmac: use container_of instead of cast
Date: Thu, 12 Jul 2012 13:47:26 +0200 [thread overview]
Message-ID: <4FFEB94E.6030808@hauke-m.de> (raw)
In-Reply-To: <20120712112007.GA12822@elgon.mountain>
On 07/12/2012 01:20 PM, Dan Carpenter wrote:
> The patch ed1dd81464f5: "brcmsmac: use container_of instead of cast"
> from Jun 30, 2012, leads to the following Smatch warning:
> drivers/net/wireless/brcm80211/brcmsmac/aiutils.c:543 ai_detach()
> warn: can 'sii' even be NULL?
>
> 533 /* may be called with core in reset */
> 534 void ai_detach(struct si_pub *sih)
> 535 {
> 536 struct si_info *sii;
> 537
> 538 struct si_pub *si_local = NULL;
> 539 memcpy(&si_local, &sih, sizeof(struct si_pub **));
I do not get what this line is used for, it looks like unneeded code,
si_local is never read.
> 540
> 541 sii = container_of(sih, struct si_info, pub);
> 542
> 543 if (sii == NULL)
> 544 return;
> 545
> 546 kfree(sii);
> 547 }
>
>
> Smatch complains because container_of() of does pointer math and the
> check for NULL only works when ->pub is first member of the si_info
> struct.
For now pub is the first member of the struct, but the null check should
be done on sih and it should be moved before the container_of line.
> Are you sure you want to free sii and not sih?
Yes sii should be freed, it is allocated in the function ai_attach()
above and there sii is casted to sih, so this only works if pub is the
first member.
> Also kfree() checks for NULL.
>
> The memcpy() is pointless.
>
> The white space is not right. There should be a blank line after the
> variable declarations.
>
> regards,
> dan carpenter
Hauke
prev parent reply other threads:[~2012-07-12 11:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-12 11:20 brcmsmac: use container_of instead of cast Dan Carpenter
2012-07-12 11:47 ` Hauke Mehrtens [this message]
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=4FFEB94E.6030808@hauke-m.de \
--to=hauke@hauke-m.de \
--cc=arend@broadcom.com \
--cc=dan.carpenter@oracle.com \
--cc=linux-wireless@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).