From: Denis Kenzior <denkenz@gmail.com>
To: Johannes Berg <johannes@sipsolutions.net>,
linux-wireless@vger.kernel.org
Subject: Re: [RESEND PATCH] nl80211: Allow GET_INTERFACE dumps to be filtered
Date: Thu, 11 Aug 2016 11:38:01 -0500 [thread overview]
Message-ID: <57ACA9E9.4020507@gmail.com> (raw)
In-Reply-To: <1470919643.12075.7.camel@sipsolutions.net>
Hi Johannes,
On 08/11/2016 07:47 AM, Johannes Berg wrote:
> On Wed, 2016-08-03 at 17:02 -0500, Denis Kenzior wrote:
>>
>> +static int nl80211_dump_interface_parse(struct sk_buff *skb,
>> + struct netlink_callback *cb,
>> + int *filter_wiphy)
>
> Wrong indentation :)
Sorry :)
Speaking of indentation, can you point me to a doc of the rules I should
follow?
>
>> static int nl80211_dump_interface(struct sk_buff *skb, struct
>> netlink_callback *cb)
>> {
>> int wp_idx = 0;
>> int if_idx = 0;
>> int wp_start = cb->args[0];
>> int if_start = cb->args[1];
>> + int filter_wiphy = cb->args[2];
>> struct cfg80211_registered_device *rdev;
>> struct wireless_dev *wdev;
>>
>> + if (!wp_start && !if_start && !filter_wiphy) {
>
> This seems incorrect - you're setting
>
>> + int ret;
>> +
>> + filter_wiphy = -1;
>> +
>> + ret = nl80211_dump_interface_parse(skb, cb,
>> &filter_wiphy);
>
> it here, but it can take the value 0, so !filter_wiphy seems wrong?
>
I can confirm that I sanity checked this patch. Both ATTR_WIPHY,
ATTR_WDEV and wildcard dumps seemed to produce expected results.
I noticed you applied this patch. Is there a particular scenario where
it goes wrong or did you convince yourself it is correct?
Regards,
-Denis
next prev parent reply other threads:[~2016-08-11 16:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-03 22:02 [RESEND PATCH] nl80211: Allow GET_INTERFACE dumps to be filtered Denis Kenzior
2016-08-11 12:47 ` Johannes Berg
2016-08-11 16:38 ` Denis Kenzior [this message]
2016-08-11 18:03 ` Johannes Berg
2016-08-11 18:20 ` Denis Kenzior
2016-08-11 18:58 ` Arend Van Spriel
2016-08-11 19:05 ` Denis Kenzior
2016-08-11 21:22 ` Arend Van Spriel
2016-08-12 5:58 ` Johannes Berg
2016-08-12 16:24 ` Denis Kenzior
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=57ACA9E9.4020507@gmail.com \
--to=denkenz@gmail.com \
--cc=johannes@sipsolutions.net \
--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).