From: Johannes Berg <johannes@sipsolutions.net>
To: Julius Volz <juliusv@google.com>
Cc: netdev@vger.kernel.org, linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] net/wireless/nl80211.c: fix endless Netlink callback loop.
Date: Tue, 08 Jul 2008 14:30:35 +0200 [thread overview]
Message-ID: <1215520235.9610.39.camel@johannes.berg> (raw)
In-Reply-To: <f4845fc0807080523o7e773de2u94c10a8739f4ddf4@mail.gmail.com> (sfid-20080708_142402_544799_C3AAFC88)
[-- Attachment #1: Type: text/plain, Size: 1430 bytes --]
> >> int idx = 0;
> >> int start = cb->args[0];
> >> struct cfg80211_registered_device *dev;
> >>
> >> mutex_lock(&cfg80211_drv_mutex);
> >> list_for_each_entry(dev, &cfg80211_drv_list, list) {
> >> - if (++idx < start)
> >> + if (++idx <= start)
> >> continue;
> >> if (nl80211_send_wiphy(skb, NETLINK_CB(cb->skb).pid,
> >> cb->nlh->nlmsg_seq, NLM_F_MULTI,
> >> - dev) < 0)
> >> + dev) < 0) {
> >> + idx--;
> >> break;
> >> + }
> >
> > I see much of the problem stemming from incrementing 'idx' at the
> > beginning of the loop, can't we just move it to the end?
>
> idx still needs to be incremented in the 'continue' case, so that
> alone wouldn't help. I'm not sure if there is a way to make this look
> more intuitive?
Good point. The only ways I can come up with add further to the already
quite deep indentation:
list_for_each_entry(...) {
if (idx > start)
if (nl80211_send_wiphy(...) < 0)
break;
idx++;
}
or hide the call into an if ():
list_for_each_entry(...) {
if (idx > start && nl80211_send_wiphy(...))
break;
idx++;
}
Not sure. I guess the code isn't touched often so your patch is fine.
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2008-07-08 12:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-08 12:02 [PATCH] net/wireless/nl80211.c: fix endless Netlink callback loop Julius Volz
2008-07-08 12:06 ` Johannes Berg
2008-07-08 12:23 ` Julius Volz
2008-07-08 12:30 ` Johannes Berg [this message]
2008-07-08 12:43 ` Julius Volz
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=1215520235.9610.39.camel@johannes.berg \
--to=johannes@sipsolutions.net \
--cc=juliusv@google.com \
--cc=linux-wireless@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).