From: Johannes Berg <johannes@sipsolutions.net>
To: Julius Volz <juliusv@google.com>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH] net/wireless/nl80211.c: fix endless Netlink callback loop.
Date: Tue, 08 Jul 2008 14:06:39 +0200 [thread overview]
Message-ID: <1215518799.9610.33.camel@johannes.berg> (raw)
In-Reply-To: <1215518539-19587-1-git-send-email-juliusv@google.com> (sfid-20080708_140237_236764_3E4EA51A)
[-- Attachment #1: Type: text/plain, Size: 1565 bytes --]
On Tue, 2008-07-08 at 14:02 +0200, Julius Volz wrote:
> Although I only tested similar code (I don't use any of this wireless
> code), the state maintainance between Netlink dump callback invocations
> seems wrong here and should lead to an endless loop. There are also other
> examples in the same file which might have the same problem. Perhaps someone
> can actually test this (or refute my logic).
>
> Take the simple example with only one element in the list (which should fit
> into the message):
> Also, iterations where the filling of an element fails should not be counted as
> completed, so idx should not be incremented in this case.
Seems to be the case on both points, however,
> --- a/net/wireless/nl80211.c
> +++ b/net/wireless/nl80211.c
> @@ -194,22 +194,24 @@ static int nl80211_send_wiphy(struct sk_buff *msg, u32 pid, u32 seq, int flags,
> static int nl80211_dump_wiphy(struct sk_buff *skb, struct netlink_callback *cb)
> {
> 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?
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:07 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 [this message]
2008-07-08 12:23 ` Julius Volz
2008-07-08 12:30 ` Johannes Berg
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=1215518799.9610.33.camel@johannes.berg \
--to=johannes@sipsolutions.net \
--cc=juliusv@google.com \
--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 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.