linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Denis Kenzior <denkenz@gmail.com>
To: Arend van Spriel <arend.vanspriel@broadcom.com>,
	linux-wireless@vger.kernel.org
Subject: Re: [PATCH] nl80211: Fix unfiltered GET_INTERFACE dumps
Date: Thu, 25 Aug 2016 16:52:26 -0500	[thread overview]
Message-ID: <57BF689A.5050406@gmail.com> (raw)
In-Reply-To: <210adf6d-287c-f836-8e2c-78f42de94dee@broadcom.com>

Hi Arend,

On 08/25/2016 04:35 PM, Arend van Spriel wrote:
> On 25-08-16 22:44, Denis Kenzior wrote:
>> dump_wiphy_parse only assigns filter_wiphy if one of the supported
>> NL80211 attributes is present.  So for unfiltered dumps, filter_wiphy
>> was always initialized to 0, and only interface 0 was dumped.
>>
>> This was introduced in commit 2d75da13fbb957e955d212555b91101cef36f0ce.
>>
>> Reported-by: Arend Van Spriel <arend.vanspriel@broadcom.com>
>
> Actually sent a patch for this issue a little earlier. I should have
> Cc'ed you explicitly, I guess.
>

Whoops.  I saw your regression report and didn't look to see if you 
fixed it :)

Looking at your patch, I'm worried that

-	int filter_wiphy = -1;
+	int filter_wiphy;

might still break things, since Johannes used:

	if (!cb->args[2]) {
		...
         } else if (cb->args[2] > 0) {
                 filter_wiphy = cb->args[2] - 1;
         }

So for unfiltered dumps, filter_wiphy would not be initialized properly 
for the second & onward call of nl80211_dump_interface. Right?

Regards,
-Denis

  reply	other threads:[~2016-08-25 21:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-25 20:44 [PATCH] nl80211: Fix unfiltered GET_INTERFACE dumps Denis Kenzior
2016-08-25 21:35 ` Arend van Spriel
2016-08-25 21:52   ` Denis Kenzior [this message]
2016-08-25 22:07     ` Arend van Spriel
2016-08-26  8:13 ` Johannes Berg

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=57BF689A.5050406@gmail.com \
    --to=denkenz@gmail.com \
    --cc=arend.vanspriel@broadcom.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 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).