From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
David Miller <davem@davemloft.net>,
Networking <netdev@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
NetFilter <netfilter-devel@vger.kernel.org>,
Jiri Pirko <jiri@mellanox.com>,
Jozsef Kadlecsik <kadlec@netfilter.org>,
Florian Westphal <fw@strlen.de>
Subject: Re: nf_flow on big-endian (was: Re: linux-next: build warning after merge of the net-next tree)
Date: Sat, 7 Dec 2019 17:41:11 +0100 [thread overview]
Message-ID: <20191207164111.fpnpoipaiadaxyde@salvia> (raw)
In-Reply-To: <CAMuHMdX8QyGkpPXfwS0EJhC6hR+gpYfvdpGWqdb=bSwJGmF7Ew@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1621 bytes --]
Hi Geert,
On Tue, Nov 26, 2019 at 12:06:03PM +0100, Geert Uytterhoeven wrote:
> On Thu, Nov 21, 2019 at 8:36 AM Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> > After merging the net-next tree, today's linux-next build (powerpc
> > allyesconfig) produced this warning:
> >
> > net/netfilter/nf_flow_table_offload.c: In function 'nf_flow_rule_match':
> > net/netfilter/nf_flow_table_offload.c:80:21: warning: unsigned conversion from 'int' to '__be16' {aka 'short unsigned int'} changes value from '327680' to '0' [-Woverflow]
> > 80 | mask->tcp.flags = TCP_FLAG_RST | TCP_FLAG_FIN;
> > | ^~~~~~~~~~~~
> >
> > Introduced by commit
> >
> > c29f74e0df7a ("netfilter: nf_flow_table: hardware offload support")
>
> This is now upstream, and must be completely broken on big-endian
> platforms.
>
> The other user of the flags field looks buggy, too
> (net/core/flow_dissector.c:__skb_flow_dissect_tcp()[*]):
>
> key_tcp->flags = (*(__be16 *) &tcp_flag_word(th) & htons(0x0FFF));
>
> Disclaimer: I'm not familiar with the code or protocol, so below are just
> my gut feelings.
>
> struct flow_dissector_key_tcp {
> __be16 flags;
> };
>
> Does this have to be __be16, i.e. does it go over the wire?
> If not, this should probably be __u16, and set using
> "be32_to_cpu(flags) >> 16"?
> If yes, "cpu_to_be16(be32_to_cpu(flags) >> 16)"?
> (Ugh, needs convenience macros)
>
> [*] ac4bb5de27010e41 ("net: flow_dissector: add support for dissection
> of tcp flags")
I'm attaching a tentative patch, please let me know this is fixing up
this issue there.
Thanks.
[-- Attachment #2: x.patch --]
[-- Type: text/x-diff, Size: 1674 bytes --]
diff --git a/include/net/flow_dissector.h b/include/net/flow_dissector.h
index b8c20e9f343e..30ad4e07ff52 100644
--- a/include/net/flow_dissector.h
+++ b/include/net/flow_dissector.h
@@ -189,10 +189,17 @@ struct flow_dissector_key_eth_addrs {
/**
* struct flow_dissector_key_tcp:
- * @flags: flags
+ * @flags: TCP flags (16-bit, including the initial Data offset field bits)
+ * @word: Data offset + reserved bits + TCP flags + window
*/
struct flow_dissector_key_tcp {
- __be16 flags;
+ union {
+ struct {
+ __be16 flags;
+ __be16 __pad;
+ };
+ __be32 flag_word;
+ };
};
/**
diff --git a/net/core/flow_dissector.c b/net/core/flow_dissector.c
index ca871657a4c4..83af4633f306 100644
--- a/net/core/flow_dissector.c
+++ b/net/core/flow_dissector.c
@@ -756,7 +756,7 @@ __skb_flow_dissect_tcp(const struct sk_buff *skb,
key_tcp = skb_flow_dissector_target(flow_dissector,
FLOW_DISSECTOR_KEY_TCP,
target_container);
- key_tcp->flags = (*(__be16 *) &tcp_flag_word(th) & htons(0x0FFF));
+ key_tcp->flag_word = tcp_flag_word(th);
}
static void
diff --git a/net/netfilter/nf_flow_table_offload.c b/net/netfilter/nf_flow_table_offload.c
index c94ebad78c5c..30205d57226d 100644
--- a/net/netfilter/nf_flow_table_offload.c
+++ b/net/netfilter/nf_flow_table_offload.c
@@ -87,8 +87,8 @@ static int nf_flow_rule_match(struct nf_flow_match *match,
switch (tuple->l4proto) {
case IPPROTO_TCP:
- key->tcp.flags = 0;
- mask->tcp.flags = TCP_FLAG_RST | TCP_FLAG_FIN;
+ key->tcp.flag_word = 0;
+ mask->tcp.flag_word = TCP_FLAG_RST | TCP_FLAG_FIN;
match->dissector.used_keys |= BIT(FLOW_DISSECTOR_KEY_TCP);
break;
case IPPROTO_UDP:
next prev parent reply other threads:[~2019-12-07 16:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-21 7:34 linux-next: build warning after merge of the net-next tree Stephen Rothwell
2019-11-26 11:06 ` nf_flow on big-endian (was: Re: linux-next: build warning after merge of the net-next tree) Geert Uytterhoeven
2019-12-07 16:41 ` Pablo Neira Ayuso [this message]
2019-12-08 10:33 ` Geert Uytterhoeven
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=20191207164111.fpnpoipaiadaxyde@salvia \
--to=pablo@netfilter.org \
--cc=davem@davemloft.net \
--cc=fw@strlen.de \
--cc=geert@linux-m68k.org \
--cc=jiri@mellanox.com \
--cc=kadlec@netfilter.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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).