From: Johannes Berg <johannes@sipsolutions.net>
To: David Miller <davem@davemloft.net>
Cc: linux-wireless@vger.kernel.org, netdev@vger.kernel.org, j@w1.fi,
dsahern@gmail.com
Subject: Re: [PATCH net 1/2] netlink: add NLA_U8_BUGGY attribute type
Date: Tue, 05 Dec 2017 18:30:10 +0100 [thread overview]
Message-ID: <1512495010.26976.24.camel@sipsolutions.net> (raw)
In-Reply-To: <20171205.114106.1013322969674769159.davem@davemloft.net>
On Tue, 2017-12-05 at 11:41 -0500, David Miller wrote:
>
> There is no reasonable interpretation for what that application is
> doing, so I think we can safely call that case as buggy.
>
> We are only trying to handle the situation where a U8 attribute
> is presented as a bonafide U32 or a correct U8.
>
> Does this make sense?
Well the application is buggy, but we don't really know in what way?
Perhaps somebody even did the equivalent of
nla_put_u32(ATTR, cpu_to_le32(x))
when they noticed it was broken on BE, and end up with a similar case
as I had above.
I don't think there's a good solution to this, applications must be
fixed anyhow. I'm just saying that I'd save the extra code and stay
compatible with applications as written today, even if they're now
broken on BE - and rely on the warning to fix it. Trying to fix it up
seems to have the potential to just break something else.
johannes
next prev parent reply other threads:[~2017-12-05 17:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-02 20:23 [PATCH net 1/2] netlink: add NLA_U8_BUGGY attribute type Johannes Berg
2017-12-02 20:23 ` [PATCH net 2/2] nl80211: use NLA_U8_BUGGY for two attributes Johannes Berg
[not found] ` <20171202202332.10205-1-johannes-cdvu00un1VgdHxzADdlk8Q@public.gmane.org>
2017-12-02 22:48 ` [PATCH net 1/2] netlink: add NLA_U8_BUGGY attribute type David Ahern
2017-12-05 16:31 ` David Miller
[not found] ` <20171205.113145.172521292247335321.davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
2017-12-05 16:34 ` Johannes Berg
2017-12-05 16:41 ` David Miller
2017-12-05 17:30 ` Johannes Berg [this message]
2017-12-05 17:40 ` David Miller
[not found] ` <20171205.124038.2265447675450126665.davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
2017-12-05 18:15 ` David Ahern
2017-12-05 19:08 ` David Miller
2017-12-05 16:41 ` David Ahern
[not found] ` <fe8e7ad5-9579-31ce-0d02-a6c8522ba366-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-12-05 16:51 ` David Miller
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=1512495010.26976.24.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=davem@davemloft.net \
--cc=dsahern@gmail.com \
--cc=j@w1.fi \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@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).