public inbox for netdev@vger.kernel.org 
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech•com>
To: Johannes Berg <johannes@sipsolutions•net>,
	linux-wireless@vger•kernel.org, netdev@vger•kernel.org
Cc: pablo@netfilter•org
Subject: Re: [RFC 2/3] genetlink: pass extended error report down
Date: Fri, 7 Apr 2017 12:27:33 -0700	[thread overview]
Message-ID: <fd15a0bb-535a-ba4f-efbb-fa566e30fcd4@candelatech.com> (raw)
In-Reply-To: <1491592343.5800.8.camel@sipsolutions.net>

On 04/07/2017 12:12 PM, Johannes Berg wrote:
> On Fri, 2017-04-07 at 11:37 -0700, Ben Greear wrote:
>>
>> I guess the error string must be constant and always available in
>> memory in this implementation?
>
> Yes.
>
>> I think it would be nice to dynamically create strings (malloc,
>> snprintf, etc) and have the err_str logic free it when done?
>
> We can think about that later, but I don't actually think it makes a
> lot of sense - if we point to the attribute and/or offset you really
> ought to have enough info to figure out what's up.

We can think about it later, but lots of things in the wifi stack
could use a descriptive message specific to the failure.  Often these
messages are much more useful if you explain why the failure conflicts
with regulatory, channel, virtual-dev combination, etc info, so that needs
to be dynamic.  The code that is failing knows, so I'd like to pass it
back to user-space.

Thanks,
Ben

-- 
Ben Greear <greearb@candelatech•com>
Candela Technologies Inc  http://www.candelatech.com

  reply	other threads:[~2017-04-07 19:27 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-07 18:26 [RFC 0/3] netlink: extended error reporting Johannes Berg
2017-04-07 18:26 ` [RFC 1/3] " Johannes Berg
2017-04-07 19:41   ` Johannes Berg
2017-04-07 18:26 ` [RFC 2/3] genetlink: pass extended error report down Johannes Berg
2017-04-07 18:37   ` Ben Greear
     [not found]     ` <25e1fb8c-22e0-d7a2-13a7-d0def5432c9e-my8/4N5VtI7c+919tysfdA@public.gmane.org>
2017-04-07 19:12       ` Johannes Berg
2017-04-07 19:27         ` Ben Greear [this message]
     [not found] ` <20170407182620.6438-1-johannes-cdvu00un1VgdHxzADdlk8Q@public.gmane.org>
2017-04-07 18:26   ` [RFC 3/3] nl80211: add a few extended error strings Johannes Berg
2017-04-07 18:53   ` [RFC 0/3] netlink: extended error reporting David Miller
     [not found]     ` <20170407.115315.23470877439489670.davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
2017-04-07 18:59       ` Johannes Berg
     [not found]         ` <1491591552.5800.1.camel-cdvu00un1VgdHxzADdlk8Q@public.gmane.org>
2017-04-07 19:06           ` Pablo Neira Ayuso
2017-04-07 19:09             ` Johannes Berg
2017-04-07 19:21               ` Pablo Neira Ayuso
2017-04-07 19:29                 ` Johannes Berg
     [not found]                   ` <1491593357.5800.13.camel-cdvu00un1VgdHxzADdlk8Q@public.gmane.org>
2017-04-07 19:45                     ` Pablo Neira Ayuso
2017-04-07 19:47                       ` Johannes Berg
2017-04-07 19:34                 ` David Miller
2017-04-07 19:22               ` David Miller
     [not found]                 ` <20170407.122223.385211483743191711.davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
2017-04-07 19:27                   ` Pablo Neira Ayuso
2017-04-07 19:29                     ` Johannes Berg
2017-04-07 19:34                     ` David Miller
2017-04-07 19:20         ` David Miller
2017-04-07 19:26           ` Johannes Berg
2017-04-07 19:35           ` Pablo Neira Ayuso
2017-04-07 19:43             ` David Miller
     [not found]               ` <20170407.124327.626442219286333933.davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
2017-04-07 19:46                 ` Johannes Berg
     [not found]                   ` <1491594406.5800.18.camel-cdvu00un1VgdHxzADdlk8Q@public.gmane.org>
2017-04-07 19:55                     ` David Miller
     [not found]                       ` <20170407.125511.1233528940652477012.davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
2017-04-07 20:27                         ` Johannes Berg
2017-04-07 19:02     ` Pablo Neira Ayuso
2017-04-07 19:06       ` 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=fd15a0bb-535a-ba4f-efbb-fa566e30fcd4@candelatech.com \
    --to=greearb@candelatech$(echo .)com \
    --cc=johannes@sipsolutions$(echo .)net \
    --cc=linux-wireless@vger$(echo .)kernel.org \
    --cc=netdev@vger$(echo .)kernel.org \
    --cc=pablo@netfilter$(echo .)org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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