From: Luciano Coelho <luciano.coelho@nokia.com>
To: ext Ido Yariv <ido@wizery.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] wl1271: Fix overflow in wl1271_boot_upload_nvs
Date: Wed, 22 Sep 2010 13:24:42 +0300 [thread overview]
Message-ID: <1285151082.22517.8.camel@chilepepper> (raw)
In-Reply-To: <1285141993-3772-1-git-send-email-ido@wizery.com>
On Wed, 2010-09-22 at 09:53 +0200, ext Ido Yariv wrote:
> Due to miscalculation of nvs_len, excessive data was sent to the
> firmware.
> Fix this by first setting nvs_ptr to point to the first NVS table,
> and computing the total size of all NVS tables accordingly.
>
> Signed-off-by: Ido Yariv <ido@wizery.com>
> ---
This looks reasonable, thanks!
But I still want to have it briefly tested before I accept it. Our
tester will try it out today or tomorrow and, if everything is okay,
I'll ack it.
> drivers/net/wireless/wl12xx/wl1271_boot.c | 17 ++++++-----------
> 1 files changed, 6 insertions(+), 11 deletions(-)
>
> diff --git a/drivers/net/wireless/wl12xx/wl1271_boot.c b/drivers/net/wireless/wl12xx/wl1271_boot.c
> index fc21db8..e5a7f04 100644
> --- a/drivers/net/wireless/wl12xx/wl1271_boot.c
> +++ b/drivers/net/wireless/wl12xx/wl1271_boot.c
> @@ -274,11 +274,11 @@ static int wl1271_boot_upload_nvs(struct wl1271 *wl)
[...]
> - nvs_aligned = kmemdup(nvs_ptr, nvs_len, GFP_KERNEL); if
> - (!nvs_aligned) return -ENOMEM;
> + nvs_aligned = kmemdup(nvs_ptr, nvs_len, GFP_KERNEL);
> + if (!nvs_aligned)
> + return -ENOMEM;
This looks pretty odd. But I checked wireless-testing and it is looking
bad there. It's not like that in our internal tree, but git blames me
for doing it in wireless-testing. :) Thanks for fixing.
--
Cheers,
Luca.
next prev parent reply other threads:[~2010-09-22 10:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-22 7:53 [PATCH] wl1271: Fix overflow in wl1271_boot_upload_nvs Ido Yariv
2010-09-22 10:24 ` Luciano Coelho [this message]
2010-09-23 7:46 ` Luciano Coelho
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=1285151082.22517.8.camel@chilepepper \
--to=luciano.coelho@nokia.com \
--cc=ido@wizery.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 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.