From: David Ahern <dsahern@gmail.com>
To: Kirill Tkhai <ktkhai@virtuozzo.com>, netdev@vger.kernel.org
Cc: idosch@idosch.org
Subject: Re: [PATCH v3 net-next 2/5] net/ipv6: Address checks need to consider the L3 domain
Date: Wed, 7 Mar 2018 12:53:54 -0700 [thread overview]
Message-ID: <afb0e946-b58f-5d63-de53-c7f5f47d774b@gmail.com> (raw)
In-Reply-To: <f2f7e7b8-7de0-1075-38f4-e3bc120262a1@gmail.com>
On 3/7/18 10:28 AM, David Ahern wrote:
> On 3/7/18 4:53 AM, Kirill Tkhai wrote:
>>> diff --git a/include/net/addrconf.h b/include/net/addrconf.h
>>> index c4185a7b0e90..132e5b95167a 100644
>>> --- a/include/net/addrconf.h
>>> +++ b/include/net/addrconf.h
>>> @@ -69,8 +69,8 @@ int addrconf_set_dstaddr(struct net *net, void __user *arg);
>>> int ipv6_chk_addr(struct net *net, const struct in6_addr *addr,
>>> const struct net_device *dev, int strict);
>>> int ipv6_chk_addr_and_flags(struct net *net, const struct in6_addr *addr,
>>> - const struct net_device *dev, int strict,
>>> - u32 banned_flags);
>>> + const struct net_device *dev, bool skip_dev_check,
>>> + int strict, u32 banned_flags);
>>
>> This function already has 5 arguments, while this patch adds one more.
>> Can't we use new flags argument for both of them?
>>
>> Also, the name of function and input parameters are already so big, that they
>> don't fit a single line already, while your patch adds more parameters.
>> Can't we make it more slim? Something like ipv6_chk_addr_fl() instead of current
>> name.
>
> I think I can combine strict and the new skip_dev_check. I am going to
> leave the function name as is.
>
Upon further review, I can not combine those flags; I missed a level of
() around the scope check which is what strict modifies. They need to be
separate arguments.
next prev parent reply other threads:[~2018-03-07 19:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-07 3:58 [PATCH v3 net-next 0/5] net/ipv6: Address checks need to consider the L3 domain David Ahern
2018-03-07 3:58 ` [PATCH v3 net-next 1/5] net/ipv6: Refactor gateway validation on route add David Ahern
2018-03-07 3:58 ` [PATCH v3 net-next 2/5] net/ipv6: Address checks need to consider the L3 domain David Ahern
2018-03-07 11:53 ` Kirill Tkhai
2018-03-07 11:59 ` Kirill Tkhai
2018-03-07 17:28 ` David Ahern
2018-03-07 19:53 ` David Ahern [this message]
2018-03-07 3:58 ` [PATCH v3 net-next 3/5] selftests: fib_tests: Use an alias for ip command David Ahern
2018-03-07 3:58 ` [PATCH v3 net-next 4/5] selftests: fib_tests: Allow user to run a specific test David Ahern
2018-03-07 3:58 ` [PATCH v3 net-next 5/5] selftests: fib_tests: Add IPv6 nexthop spec tests David Ahern
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=afb0e946-b58f-5d63-de53-c7f5f47d774b@gmail.com \
--to=dsahern@gmail.com \
--cc=idosch@idosch.org \
--cc=ktkhai@virtuozzo.com \
--cc=netdev@vger.kernel.org \
/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).