From: Johannes Berg <johannes@sipsolutions.net> To: Jiri Pirko <jiri@resnulli.us> Cc: linux-wireless@vger.kernel.org, netdev@vger.kernel.org, pablo@netfilter.org, Jamal Hadi Salim <jhs@mojatatu.com>, Jiri Benc <jbenc@redhat.com>, David Ahern <dsa@cumulusnetworks.com> Subject: Re: [PATCH 1/5] netlink: extended ACK reporting Date: Sat, 08 Apr 2017 22:13:14 +0200 [thread overview] Message-ID: <1491682394.2379.1.camel@sipsolutions.net> (raw) In-Reply-To: <20170408184008.GB1900@nanopsycho> (sfid-20170408_204012_186615_65B86B3C) On Sat, 2017-04-08 at 20:40 +0200, Jiri Pirko wrote: > > I think I'll leave it like this - if anyone really wants to say > > "attribute 0 is missing" then we can add a flag later... The UAPI > > does > > take this into account by not including the attribute at all if the > > data is invalid, so 0 in the userspace API can be done > > It a known issue, should be fixed right now. We are in no hurry. This > waited +15 years to be done, no harm in couple more days. It's not about any timing or anything - I simply think the likelihood that this will be needed is zero, because almost no netlink family uses attribute zero, those that do use it are older ones unlikely to be updated to start with, and *then* needing to indicate that attribute 0 is missing? Not going to happen. The extra code needed to handle this is therefore wasted. > Also, could you please attach a patch to iproute2 for example which > would make use of this. I just want to make sure it clicks. No, I'm not going to do that. If you want it, please do it yourself. I've done the testing on a slightly modified iw, but even there haven't done any pretty-printing or parsing, just made sure the attributes show up properly (by dumping them in hex). johannes
WARNING: multiple messages have this Message-ID (diff)
From: Johannes Berg <johannes-cdvu00un1VgdHxzADdlk8Q@public.gmane.org> To: Jiri Pirko <jiri-rHqAuBHg3fBzbRFIqnYvSA@public.gmane.org> Cc: linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, pablo-Cap9r6Oaw4JrovVCs/uTlw@public.gmane.org, Jamal Hadi Salim <jhs-jkUAjuhPggJWk0Htik3J/w@public.gmane.org>, Jiri Benc <jbenc-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>, David Ahern <dsa-qUQiAmfTcIp+XZJcv9eMoEEOCMrvLtNR@public.gmane.org> Subject: Re: [PATCH 1/5] netlink: extended ACK reporting Date: Sat, 08 Apr 2017 22:13:14 +0200 [thread overview] Message-ID: <1491682394.2379.1.camel@sipsolutions.net> (raw) In-Reply-To: <20170408184008.GB1900@nanopsycho> (sfid-20170408_204012_186615_65B86B3C) On Sat, 2017-04-08 at 20:40 +0200, Jiri Pirko wrote: > > I think I'll leave it like this - if anyone really wants to say > > "attribute 0 is missing" then we can add a flag later... The UAPI > > does > > take this into account by not including the attribute at all if the > > data is invalid, so 0 in the userspace API can be done > > It a known issue, should be fixed right now. We are in no hurry. This > waited +15 years to be done, no harm in couple more days. It's not about any timing or anything - I simply think the likelihood that this will be needed is zero, because almost no netlink family uses attribute zero, those that do use it are older ones unlikely to be updated to start with, and *then* needing to indicate that attribute 0 is missing? Not going to happen. The extra code needed to handle this is therefore wasted. > Also, could you please attach a patch to iproute2 for example which > would make use of this. I just want to make sure it clicks. No, I'm not going to do that. If you want it, please do it yourself. I've done the testing on a slightly modified iw, but even there haven't done any pretty-printing or parsing, just made sure the attributes show up properly (by dumping them in hex). johannes
next prev parent reply other threads:[~2017-04-08 20:13 UTC|newest] Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top 2017-04-08 17:48 [PATCH 0/5] extended netlink ACK reporting Johannes Berg 2017-04-08 17:48 ` Johannes Berg 2017-04-08 17:48 ` [PATCH 1/5] netlink: extended " Johannes Berg 2017-04-08 18:26 ` David Ahern 2017-04-08 18:34 ` Jiri Pirko 2017-04-08 18:37 ` Johannes Berg 2017-04-08 18:40 ` Jiri Pirko 2017-04-08 20:13 ` Johannes Berg [this message] 2017-04-08 20:13 ` Johannes Berg 2017-04-09 17:43 ` David Ahern 2017-04-09 17:43 ` David Ahern 2017-04-10 6:18 ` Johannes Berg 2017-04-13 13:27 ` Nicolas Dichtel 2017-04-13 13:27 ` Nicolas Dichtel 2017-04-13 13:29 ` Johannes Berg 2017-04-13 14:05 ` Nicolas Dichtel 2017-04-13 14:05 ` Nicolas Dichtel 2017-04-13 19:24 ` Johannes Berg 2017-04-13 19:24 ` Johannes Berg [not found] ` <1492111480.29526.7.camel-cdvu00un1VgdHxzADdlk8Q@public.gmane.org> 2017-04-13 21:44 ` Joe Stringer 2017-04-18 9:41 ` Johannes Berg 2017-04-18 9:41 ` Johannes Berg 2017-04-18 23:46 ` Joe Stringer 2017-04-18 23:46 ` Joe Stringer 2017-04-16 14:40 ` second wave of netlink " Jamal Hadi Salim 2017-04-16 14:40 ` Jamal Hadi Salim 2017-04-16 14:45 ` David Ahern 2017-04-16 14:45 ` David Ahern 2017-04-16 14:48 ` Jamal Hadi Salim 2017-04-16 14:48 ` Jamal Hadi Salim 2017-04-16 14:50 ` David Ahern 2017-04-16 14:50 ` David Ahern 2017-04-16 16:55 ` David Ahern 2017-04-16 16:55 ` David Ahern 2017-04-08 18:36 ` [PATCH 1/5] netlink: " David Ahern 2017-04-08 18:36 ` David Ahern 2017-04-08 18:37 ` Johannes Berg 2017-04-08 18:37 ` Johannes Berg 2017-04-08 20:14 ` David Ahern 2017-04-08 17:48 ` [PATCH 2/5] genetlink: pass extended ACK report down Johannes Berg 2017-04-08 17:48 ` [PATCH 3/5] netlink: allow sending extended ACK with cookie on success Johannes Berg 2017-04-08 17:48 ` Johannes Berg 2017-04-08 17:48 ` [PATCH 4/5] netlink: pass extended ACK struct to parsing functions Johannes Berg 2017-04-08 18:50 ` David Ahern 2017-04-08 18:50 ` David Ahern 2017-04-08 20:15 ` Johannes Berg 2017-04-08 20:15 ` Johannes Berg 2017-04-08 17:49 ` [PATCH 5/5] netlink: pass extended ACK struct where available 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=1491682394.2379.1.camel@sipsolutions.net \ --to=johannes@sipsolutions.net \ --cc=dsa@cumulusnetworks.com \ --cc=jbenc@redhat.com \ --cc=jhs@mojatatu.com \ --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: linkBe 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.