From: Hangbin Liu <liuhangbin@gmail.com>
To: Nikolay Aleksandrov <nikolay@nvidia.com>
Cc: netdev@vger.kernel.org, Jay Vosburgh <j.vosburgh@gmail.com>,
Veaceslav Falico <vfalico@gmail.com>,
Andy Gospodarek <andy@greyhouse.net>,
"David S . Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>, David Ahern <dsahern@gmail.com>
Subject: Re: [PATCH RFC net-next 3/5] bonding: add ip6_addr for bond_opt_value
Date: Thu, 27 Jan 2022 15:02:51 +0800 [thread overview]
Message-ID: <YfJDm4f2xURqz5v8@Laptop-X1> (raw)
In-Reply-To: <bc3403db-4380-9d84-b507-babdeb929664@nvidia.com>
On Wed, Jan 26, 2022 at 01:35:46PM +0200, Nikolay Aleksandrov wrote:
> > diff --git a/include/net/bond_options.h b/include/net/bond_options.h
> > index dd75c071f67e..a9e68e88ff73 100644
> > --- a/include/net/bond_options.h
> > +++ b/include/net/bond_options.h
> > @@ -79,6 +79,7 @@ struct bond_opt_value {
> > char *string;
> > u64 value;
> > u32 flags;
> > + struct in6_addr ip6_addr;
> > };
> >
> > struct bonding;
> > @@ -118,17 +119,20 @@ const struct bond_opt_value *bond_opt_get_val(unsigned int option, u64 val);
> > * When value is ULLONG_MAX then string will be used.
> > */
> > static inline void __bond_opt_init(struct bond_opt_value *optval,
> > - char *string, u64 value)
> > + char *string, u64 value, struct in6_addr *addr)
> > {
> > memset(optval, 0, sizeof(*optval));
> > optval->value = ULLONG_MAX;
> > - if (value == ULLONG_MAX)
> > + if (string)
> > optval->string = string;
> > + else if (addr)
> > + optval->ip6_addr = *addr;
> > else
> > optval->value = value;
> > }
> > -#define bond_opt_initval(optval, value) __bond_opt_init(optval, NULL, value)
> > -#define bond_opt_initstr(optval, str) __bond_opt_init(optval, str, ULLONG_MAX)
> > +#define bond_opt_initval(optval, value) __bond_opt_init(optval, NULL, value, NULL)
> > +#define bond_opt_initstr(optval, str) __bond_opt_init(optval, str, ULLONG_MAX, NULL)
> > +#define bond_opt_initaddr(optval, addr) __bond_opt_init(optval, NULL, ULLONG_MAX, addr)
> >
> > void bond_option_arp_ip_targets_clear(struct bonding *bond);
> >
>
> Please don't add arbitrary fields to struct bond_opt_value. As the comment above it states:
> /* This structure is used for storing option values and for passing option
> * values when changing an option. The logic when used as an arg is as follows:
> * - if string != NULL -> parse it, if the opt is RAW type then return it, else
> * return the parse result
> * - if string == NULL -> parse value
> */
>
> You can use an anonymous union to extend value's size and use the extra room for storage
> only, that should keep most of the current logic intact.
Hi Nikolay,
The current checking for string is (value == ULLONG_MAX). If we use
a union for IPv6 address and value, what about the address like
ffff:ffff:ffff:ffff::/64?
Thanks
Hangbin
next prev parent reply other threads:[~2022-01-27 7:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-26 7:35 [PATCH RFC net-next 0/5] bonding: add IPv6 NS/NA monitor support Hangbin Liu
2022-01-26 7:35 ` [PATCH RFC net-next 1/5] ipv6: separate ndisc_ns_create() from ndisc_send_ns() Hangbin Liu
2022-01-26 7:35 ` [PATCH RFC net-next 2/5] Bonding: split bond_handle_vlan from bond_arp_send Hangbin Liu
2022-01-26 7:35 ` [PATCH RFC net-next 3/5] bonding: add ip6_addr for bond_opt_value Hangbin Liu
2022-01-26 11:35 ` Nikolay Aleksandrov
2022-01-27 7:02 ` Hangbin Liu [this message]
2022-01-27 8:56 ` Nikolay Aleksandrov
2022-01-27 12:09 ` Hangbin Liu
2022-01-27 12:14 ` Nikolay Aleksandrov
2022-01-28 8:04 ` Hangbin Liu
2022-01-26 7:35 ` [PATCH RFC net-next 4/5] bonding: add new parameter ns_targets Hangbin Liu
2022-01-26 7:35 ` [PATCH RFC net-next 5/5] bonding: add new option ns_ip6_target Hangbin Liu
2022-01-26 11:47 ` [PATCH RFC net-next 0/5] bonding: add IPv6 NS/NA monitor support Nikolay Aleksandrov
2022-01-27 7:13 ` 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=YfJDm4f2xURqz5v8@Laptop-X1 \
--to=liuhangbin@gmail.com \
--cc=andy@greyhouse.net \
--cc=davem@davemloft.net \
--cc=dsahern@gmail.com \
--cc=j.vosburgh@gmail.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nikolay@nvidia.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