From: Arnd Bergmann <arnd@arndb.de>
To: linux-arm-kernel@lists.infradead.org
Cc: Russell King - ARM Linux <linux@arm.linux.org.uk>,
Jouni Malinen <j@w1.fi>,
netdev@vger.kernel.org, linux-wireless@vger.kernel.org,
linux-kernel@vger.kernel.org, Kalle Valo <kvalo@codeaurora.org>
Subject: Re: [PATCH] hostap: avoid uninitialized variable use in hfa384x_get_rid
Date: Thu, 28 Jan 2016 22:57:07 +0100 [thread overview]
Message-ID: <2640544.07pTZp3kGe@wuerfel> (raw)
In-Reply-To: <20160127192612.GD10826@n2100.arm.linux.org.uk>
On Wednesday 27 January 2016 19:26:13 Russell King - ARM Linux wrote:
> On Wed, Jan 27, 2016 at 02:45:26PM +0100, Arnd Bergmann wrote:
> So, why give the compiler a hard time as you're doing, why make the code
> harder to read. What's wrong with:
>
> spin_lock_bh(&local->baplock);
>
> res = hfa384x_setup_bap(dev, BAP0, rid, 0);
> if (res)
> goto unlock;
>
> res = hfa384x_from_bap(dev, BAP0, &rec, sizeof(rec));
> if (res)
> goto unlock;
>
> if (le16_to_cpu(rec.len) == 0) {
> /* RID not available */
> res = -ENODATA;
> goto unlock;
> }
>
> rlen = (le16_to_cpu(rec.len) - 1) * 2;
> if (exact_len && rlen != len) {
> printk(KERN_DEBUG "%s: hfa384x_get_rid - RID len mismatch: rid=0x%04x, len=%d (expected %d)\n",
> dev->name, rid, rlen, len);
> res = -ENODATA;
> goto unlock;
> }
>
> res = hfa384x_from_bap(dev, BAP0, buf, len);
> unlock:
> spin_unlock_bh(&local->baplock);
>
> ?
>
Good idea, I'll send a new version.
Arnd
prev parent reply other threads:[~2016-01-28 21:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-27 13:45 [PATCH] hostap: avoid uninitialized variable use in hfa384x_get_rid Arnd Bergmann
2016-01-27 19:26 ` Russell King - ARM Linux
2016-01-28 21:57 ` Arnd Bergmann [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=2640544.07pTZp3kGe@wuerfel \
--to=arnd@arndb.de \
--cc=j@w1.fi \
--cc=kvalo@codeaurora.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--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