[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <fb5cbecc-219b-b65c-cdc0-daddf6017d11@iogearbox.net>
Date: Tue, 10 Jul 2018 20:13:44 +0200
From: Daniel Borkmann <daniel@...earbox.net>
To: Martin KaFai Lau <kafai@...com>,
David Laight <David.Laight@...LAB.COM>
Cc: Okash Khawaja <osk@...com>, Alexei Starovoitov <ast@...nel.org>,
Yonghong Song <yhs@...com>,
Jakub Kicinski <jakub.kicinski@...ronome.com>,
"David S. Miller" <davem@...emloft.net>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"kernel-team@...com" <kernel-team@...com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH bpf 1/1] bpf: btf: Fix bitfield extraction for big endian
On 07/10/2018 07:18 PM, Martin KaFai Lau wrote:
[...]
> I would prefer to keep it as u16 which is the max width that is allowed for
> this field in the wire format. Keeping the usage consistent can avoid
> accidentally incorrect offsetting or writing wrong data out in other
> cases.
+1
Powered by blists - more mailing lists