From: Jonathan Toppins <jtoppins@redhat.com>
To: Hangbin Liu <liuhangbin@gmail.com>,
Jay Vosburgh <jay.vosburgh@canonical.com>
Cc: netdev@vger.kernel.org, Veaceslav Falico <vfalico@gmail.com>,
Andy Gospodarek <andy@greyhouse.net>,
"David S . Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
Eric Dumazet <eric.dumazet@gmail.com>,
Paolo Abeni <pabeni@redhat.com>, Li Liang <liali@redhat.com>
Subject: Re: [PATCH net] bonding: show NS IPv6 targets in proc master info
Date: Sun, 29 May 2022 23:35:21 -0400 [thread overview]
Message-ID: <734fdf5d-2647-274c-92b5-dab81abe4cbb@redhat.com> (raw)
In-Reply-To: <YpQzd8BqidUc4IsT@Laptop-X1>
On 5/29/22 23:01, Hangbin Liu wrote:
> On Fri, May 27, 2022 at 04:21:45PM -0700, Jay Vosburgh wrote:
>> Jonathan Toppins <jtoppins@redhat.com> wrote:
>>
>>> On 5/27/22 02:44, Hangbin Liu wrote:
>>>> When adding bond new parameter ns_targets. I forgot to print this
>>>> in bond master proc info. After updating, the bond master info will looks
>>> look ---^
>>>> like:
>>>> ARP IP target/s (n.n.n.n form): 192.168.1.254
>>>> NS IPv6 target/s (XX::XX form): 2022::1, 2022::2
>>>> Fixes: 4e24be018eb9 ("bonding: add new parameter ns_targets")
>>>> Reported-by: Li Liang <liali@redhat.com>
>>>> Signed-off-by: Hangbin Liu <liuhangbin@gmail.com>
>>>> ---
>>>> drivers/net/bonding/bond_procfs.c | 13 +++++++++++++
>>>> 1 file changed, 13 insertions(+)
>>>> diff --git a/drivers/net/bonding/bond_procfs.c
>>>> b/drivers/net/bonding/bond_procfs.c
>>>> index cfe37be42be4..b6c012270e2e 100644
>>>> --- a/drivers/net/bonding/bond_procfs.c
>>>> +++ b/drivers/net/bonding/bond_procfs.c
>>>> @@ -129,6 +129,19 @@ static void bond_info_show_master(struct seq_file *seq)
>>>> printed = 1;
>>>> }
>>>> seq_printf(seq, "\n");
>>>
>>> Does this need to be guarded by "#if IS_ENABLED(CONFIG_IPV6)"?
>>
>> On looking at it, the definition of ns_targets in struct
>> bond_params isn't gated by CONFIG_IPV6, either (and is 256 bytes for
>> just ns_targets).
>>
>> I suspect this will all compile even if CONFIG_IPV6 isn't
>> enabled, since functions like ipv6_addr_any are defined regardless of
>> the CONFIG_IPV6 setting, but it's dead code that shouldn't be built if
>> CONFIG_IPV6 isn't set.
>
> Yes, I didn't protect the code if if could be build without CONFIG_IPV6.
> e.g. function bond_get_targets_ip6(). Do you think if I should also
> add the condition for bond_get_targets_ip6() and ns_targets in struct
> bond_params?
Yes, if the code that will use the entries in `struct bonding` and
`struct bond_params` is going to be compiled out these entries should be
compiled out as well.
Also, I was looking over the code in bond_options.c:bond_opts, and the
entry `BOND_OPT_NS_TARGETS` is the only bonding option that will be left
uninitialized if IPv6 is disabled. Does the bonding options infra handle
this correctly or do you need a dummy set of values when IPv6 is disabled?
next prev parent reply other threads:[~2022-05-30 3:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-27 6:44 [PATCH net] bonding: show NS IPv6 targets in proc master info Hangbin Liu
2022-05-27 14:13 ` Jonathan Toppins
2022-05-27 23:21 ` Jay Vosburgh
2022-05-30 3:01 ` Hangbin Liu
2022-05-30 3:35 ` Jonathan Toppins [this message]
2022-05-30 5:41 ` Hangbin Liu
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=734fdf5d-2647-274c-92b5-dab81abe4cbb@redhat.com \
--to=jtoppins@redhat.com \
--cc=andy@greyhouse.net \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=jay.vosburgh@canonical.com \
--cc=kuba@kernel.org \
--cc=liali@redhat.com \
--cc=liuhangbin@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=vfalico@gmail.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;
as well as URLs for NNTP newsgroup(s).