From: Veaceslav Falico <vfalico@redhat.com>
To: Ding Tianhong <dingtianhong@huawei.com>
Cc: Jay Vosburgh <fubar@us.ibm.com>,
Andy Gospodarek <andy@greyhouse.net>,
"David S. Miller" <davem@davemloft.net>,
Nikolay Aleksandrov <nikolay@redhat.com>,
Netdev <netdev@vger.kernel.org>
Subject: Re: [PATCH net v2] bonding: add ip checks when store ip target
Date: Thu, 14 Nov 2013 11:10:28 +0100 [thread overview]
Message-ID: <20131114101028.GQ19702@redhat.com> (raw)
In-Reply-To: <52843700.2040509@huawei.com>
On Thu, Nov 14, 2013 at 10:35:44AM +0800, Ding Tianhong wrote:
...snip...
>- newtarget = in_aton(buf + 1);
>+ if (!in4_pton(buf + 1, -1, (u8 *)&newtarget, -1, NULL) ||
>+ newtarget == 0) {
Good catch on that newtarget verification, forgot to add it. However, the
previous checked not only for all-zeroes, but also for the broadcast, so
it'd be great if you could maintain the previous functionality/checks.
Or, even better, you could do something like SCTP does in
IS_IPV4_UNUSABLE_ADDRESS():
353 #define IS_IPV4_UNUSABLE_ADDRESS(a) \
354 ((htonl(INADDR_BROADCAST) == a) || \
355 ipv4_is_multicast(a) || \
356 ipv4_is_zeronet(a) || \
357 ipv4_is_test_198(a) || \
358 ipv4_is_anycast_6to4(a))
It's up to you, though, I think that either way works good - it's
sysadmin's job to know which addresses can/have to be used.
Also, fix the identation.
Thanks!
>+ pr_err("%s: invalid ARP target %pI4 specified for addition\n",
>+ bond->dev->name, &newtarget);
>+ goto out;
>+ }
> /* look for adds */
> if (buf[0] == '+') {
>- if ((newtarget == 0) || (newtarget == htonl(INADDR_BROADCAST))) {
>- pr_err("%s: invalid ARP target %pI4 specified for addition\n",
>- bond->dev->name, &newtarget);
>- goto out;
>- }
>-
> if (bond_get_targets_ip(targets, newtarget) != -1) { /* dup */
> pr_err("%s: ARP target %pI4 is already present\n",
> bond->dev->name, &newtarget);
...snip...
next prev parent reply other threads:[~2013-11-14 10:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-14 2:35 [PATCH net v2] bonding: add ip checks when store ip target Ding Tianhong
2013-11-14 10:10 ` Veaceslav Falico [this message]
2013-11-14 10:23 ` Ding Tianhong
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=20131114101028.GQ19702@redhat.com \
--to=vfalico@redhat.com \
--cc=andy@greyhouse.net \
--cc=davem@davemloft.net \
--cc=dingtianhong@huawei.com \
--cc=fubar@us.ibm.com \
--cc=netdev@vger.kernel.org \
--cc=nikolay@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.