From: Matthieu Baerts <matthieu.baerts@tessares.net>
To: Ferenc Fejes <fejes@inf.elte.hu>
Cc: netdev@vger.kernel.org, Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Martin KaFai Lau <kafai@fb.com>, Song Liu <songliubraving@fb.com>,
Yonghong Song <yhs@fb.com>, Andrii Nakryiko <andriin@fb.com>,
John Fastabend <john.fastabend@gmail.com>,
KP Singh <kpsingh@chromium.org>,
"David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
bpf@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH bpf] bpf: fix unused-var without NETDEVICES
Date: Wed, 3 Jun 2020 11:12:01 +0200 [thread overview]
Message-ID: <1cb3266c-7c8c-ebe6-0b6e-6d970e0adbd1@tessares.net> (raw)
In-Reply-To: <CAAej5NZZNg+0EbZsa-SrP0S_sOPMqdzgQ9hS8z6DYpQp9G+yhw@mail.gmail.com>
Hi Ferenc,
On 03/06/2020 10:56, Ferenc Fejes wrote:
> Matthieu Baerts <matthieu.baerts@tessares.net> ezt írta (időpont:
> 2020. jún. 3., Sze, 10:11):
>>
>> A recent commit added new variables only used if CONFIG_NETDEVICES is
>> set.
>
> Thank you for noticing and fixed this!
>
>> A simple fix is to only declare these variables if the same
>> condition is valid.
>>
>> Other solutions could be to move the code related to SO_BINDTODEVICE
>> option from _bpf_setsockopt() function to a dedicated one or only
>> declare these variables in the related "case" section.
>
> Yes thats indeed a cleaner way to approach this. I will prepare a fix for that.
I should have maybe added that I didn't take this approach because in
the rest of the code, I don't see that variables are declared only in a
"case" section (no "{" ... "}" after "case") and code is generally not
moved into a dedicated function in these big switch/cases. But maybe it
makes sense here because of the #ifdef!
At the end, I took the simple approach because it is for -net.
In other words, I don't know what maintainers would prefer here but I am
happy to see any another solutions implemented to remove these compiler
warnings :)
Cheers,
Matt
--
Matthieu Baerts | R&D Engineer
matthieu.baerts@tessares.net
Tessares SA | Hybrid Access Solutions
www.tessares.net
1 Avenue Jean Monnet, 1348 Louvain-la-Neuve, Belgium
next prev parent reply other threads:[~2020-06-03 9:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-03 8:11 Matthieu Baerts
2020-06-03 8:56 ` Ferenc Fejes
2020-06-03 9:12 ` Matthieu Baerts [this message]
2020-06-03 18:14 ` Alexei Starovoitov
2020-06-03 18:41 ` Matthieu Baerts
2020-06-03 18:43 ` Alexei Starovoitov
2020-06-03 19:03 ` [PATCH bpf v2] " Matthieu Baerts
2020-06-03 20:45 ` Song Liu
2020-06-04 20:53 ` Daniel Borkmann
2020-06-03 18:59 ` [PATCH bpf] " Ferenc Fejes
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=1cb3266c-7c8c-ebe6-0b6e-6d970e0adbd1@tessares.net \
--to=matthieu.baerts@tessares.net \
--cc=andriin@fb.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=fejes@inf.elte.hu \
--cc=john.fastabend@gmail.com \
--cc=kafai@fb.com \
--cc=kpsingh@chromium.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=songliubraving@fb.com \
--cc=yhs@fb.com \
/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
all inboxes | Powered by JetHome®