All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: linux-wireless@vger.kernel.org, netdev@vger.kernel.org
Cc: pablo@netfilter.org
Subject: Re: [RFC 1/3] netlink: extended error reporting
Date: Fri, 07 Apr 2017 21:41:03 +0200	[thread overview]
Message-ID: <1491594063.5800.15.camel@sipsolutions.net> (raw)
In-Reply-To: <20170407182620.6438-2-johannes@sipsolutions.net> (sfid-20170407_202644_889879_CEBB983B)

On Fri, 2017-04-07 at 20:26 +0200, Johannes Berg wrote:
> 
> +	if (nlk->flags & NETLINK_F_EXT_ACK) {
> +		if (exterr && exterr->msg)
> +			WARN_ON(nla_put_string(skb,
> NLMSGERR_ATTR_MSG,
> +					       exterr->msg));
> +		if (exterr && exterr->msg_offset)
> +			WARN_ON(nla_put_u32(skb, NLMSGERR_ATTR_OFFS,
> +					    exterr->msg_offset));
> +		if (exterr && exterr->attr)
> +			WARN_ON(nla_put_u16(skb, NLMSGERR_ATTR_ATTR,
> +					    exterr->attr));
> +	}

I forgot to check (err != 0) here, which can cause inconsistencies -
noticed that while just adding the error case Jamal wanted. I'll send
out that as a separate patch, and squash it later when I resubmit.

johannes

  reply	other threads:[~2017-04-07 19:41 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 [this message]
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
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=1491594063.5800.15.camel@sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --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.