From: Michael Buesch <mb@bu3sch.de>
To: Stefano Brivio <stefano.brivio@polimi.it>
Cc: "John W. Linville" <linville@tuxdriver.com>,
Larry Finger <larry.finger@lwfinger.net>,
linux-wireless@vger.kernel.org,
Mattias Nissler <mattias.nissler@gmx.de>
Subject: Re: [PATCH 2/2] rc80211-pid: add sanity check
Date: Sat, 26 Jan 2008 12:19:32 +0100 [thread overview]
Message-ID: <200801261219.34805.mb@bu3sch.de> (raw)
In-Reply-To: <20080126040534.005e6736@morte>
On Saturday 26 January 2008 04:05:34 Stefano Brivio wrote:
> From: Larry Finger <larry.finger@lwfinger.net>
>
> Add a sanity check in rate_control_pid_adjust_rate(). Thanks to Larry Finger
> for suggesting this and reporting a related bug.
>
> Signed-off-by: Stefano Brivio <stefano.brivio@polimi.it>
> NOT-Signed-off-by: Larry Finger <larry.finger@lwfinger.net>
> ---
> Index: wireless-2.6/net/mac80211/rc80211_pid_algo.c
> ===================================================================
> --- wireless-2.6.orig/net/mac80211/rc80211_pid_algo.c
> +++ wireless-2.6/net/mac80211/rc80211_pid_algo.c
> @@ -128,6 +128,11 @@ static void rate_control_pid_adjust_rate
> }
>
> newidx += back;
> +
> + if (newidx < 0 || newidx >= sband->n_bitrates) {
> + WARN_ON(1);
> + break;
> + }
> }
Just you know, you can also do this kind of check this way:
if (WARN_ON(newidx < 0 || newidx >= sband->n_bitrates))
break;
This way you have an implicite unlikely() and less lines. :)
But you don't need to respin the patch. I'm also OK with the above.
This is just informational. ;)
--
Greetings Michael.
next prev parent reply other threads:[~2008-01-26 11:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-26 3:05 [PATCH 2/2] rc80211-pid: add sanity check Stefano Brivio
2008-01-26 3:20 ` Larry Finger
2008-01-26 11:19 ` Michael Buesch [this message]
2008-01-26 19:40 ` Lars
2008-01-27 12:42 ` Stefano Brivio
2008-01-27 13:22 ` mac80211 refcounting bug was: " Stefano Brivio
2008-01-27 14:32 ` Stefano Brivio
2008-01-27 13:53 ` Lars Ericsson
2008-01-27 16:56 ` Larry Finger
2008-01-27 18:51 ` Stefano Brivio
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=200801261219.34805.mb@bu3sch.de \
--to=mb@bu3sch.de \
--cc=larry.finger@lwfinger.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mattias.nissler@gmx.de \
--cc=stefano.brivio@polimi.it \
/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).