All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: David Miller <davem@davemloft.net>, pablo@netfilter.org
Cc: linux-wireless@vger.kernel.org, netdev@vger.kernel.org, jiri@resnulli.us
Subject: Re: [RFC 0/3] netlink: extended error reporting
Date: Fri, 07 Apr 2017 21:46:46 +0200	[thread overview]
Message-ID: <1491594406.5800.18.camel@sipsolutions.net> (raw)
In-Reply-To: <20170407.124327.626442219286333933.davem@davemloft.net>

On Fri, 2017-04-07 at 12:43 -0700, David Miller wrote:
> 
> I have no strong opinions about string length.
> 
> In my opinion, I would like to believe that if someone tried to get a
> networking patch applied that emitted a rediculously long string then
> we would give them feedback about how that is not acceptable.  Right?

Agree with this, I don't really see much point in adding an extra
warning. There's an implicit (multi-KB though) limit as well in the
message size ;-)

> I suspect that someone will eventually give us a hard time about the
> strings wrt. internationalization. :-) It's solvable at least
> partially in userspace I suppose.

I tend to think of the strings more of a debugging aid, but that's a
good point.

Perhaps we should have a macro that has the strings - similar to the
inline function I put into netlink - but if we make that a macro we can
put the strings into a separate section to be able to find them more
easily for later translation, and optionally even omit them entirely
(to satisfy the kernel tinification folks)?

johannes

WARNING: multiple messages have this Message-ID (diff)
From: Johannes Berg <johannes-cdvu00un1VgdHxzADdlk8Q@public.gmane.org>
To: David Miller <davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>,
	pablo-Cap9r6Oaw4JrovVCs/uTlw@public.gmane.org
Cc: linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	jiri-rHqAuBHg3fBzbRFIqnYvSA@public.gmane.org
Subject: Re: [RFC 0/3] netlink: extended error reporting
Date: Fri, 07 Apr 2017 21:46:46 +0200	[thread overview]
Message-ID: <1491594406.5800.18.camel@sipsolutions.net> (raw)
In-Reply-To: <20170407.124327.626442219286333933.davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>

On Fri, 2017-04-07 at 12:43 -0700, David Miller wrote:
> 
> I have no strong opinions about string length.
> 
> In my opinion, I would like to believe that if someone tried to get a
> networking patch applied that emitted a rediculously long string then
> we would give them feedback about how that is not acceptable.  Right?

Agree with this, I don't really see much point in adding an extra
warning. There's an implicit (multi-KB though) limit as well in the
message size ;-)

> I suspect that someone will eventually give us a hard time about the
> strings wrt. internationalization. :-) It's solvable at least
> partially in userspace I suppose.

I tend to think of the strings more of a debugging aid, but that's a
good point.

Perhaps we should have a macro that has the strings - similar to the
inline function I put into netlink - but if we make that a macro we can
put the strings into a separate section to be able to find them more
easily for later translation, and optionally even omit them entirely
(to satisfy the kernel tinification folks)?

johannes

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

Thread overview: 45+ 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
2017-04-07 19:12     ` Johannes Berg
2017-04-07 19:12       ` Johannes Berg
2017-04-07 19:27       ` Ben Greear
2017-04-07 18:26 ` [RFC 3/3] nl80211: add a few extended error strings Johannes Berg
2017-04-07 18:26   ` Johannes Berg
2017-04-07 18:53 ` [RFC 0/3] netlink: extended error reporting David Miller
2017-04-07 18:53   ` David Miller
2017-04-07 18:59   ` Johannes Berg
2017-04-07 18:59     ` Johannes Berg
2017-04-07 19:06     ` Pablo Neira Ayuso
2017-04-07 19:06       ` Pablo Neira Ayuso
2017-04-07 19:09       ` Johannes Berg
2017-04-07 19:09         ` Johannes Berg
2017-04-07 19:21         ` Pablo Neira Ayuso
2017-04-07 19:29           ` Johannes Berg
2017-04-07 19:29             ` Johannes Berg
2017-04-07 19:45             ` Pablo Neira Ayuso
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:34             ` David Miller
2017-04-07 19:22         ` David Miller
2017-04-07 19:27           ` Pablo Neira Ayuso
2017-04-07 19:27             ` Pablo Neira Ayuso
2017-04-07 19:29             ` Johannes Berg
2017-04-07 19:29               ` Johannes Berg
2017-04-07 19:34             ` David Miller
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
2017-04-07 19:46           ` Johannes Berg [this message]
2017-04-07 19:46             ` Johannes Berg
2017-04-07 19:55             ` David Miller
2017-04-07 19:55               ` David Miller
2017-04-07 20:27               ` Johannes Berg
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=1491594406.5800.18.camel@sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=davem@davemloft.net \
    --cc=jiri@resnulli.us \
    --cc=linux-wireless@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pablo@netfilter.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.