All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jiri Benc <jbenc@redhat.com>
To: Mahesh Bandewar <maheshb@google.com>
Cc: David Miller <davem@davemloft.net>,
	linux-netdev <netdev@vger.kernel.org>,
	dcbw@redhat.com
Subject: Re: [PATCH net] ipvlan: fix addr hash list corruption
Date: Thu, 26 Mar 2015 00:49:09 +0100	[thread overview]
Message-ID: <20150326004910.1259bed5@griffin> (raw)
In-Reply-To: <20150326002154.3e179fec@griffin>

On Thu, 26 Mar 2015 00:21:53 +0100, Jiri Benc wrote:
> On Wed, 25 Mar 2015 11:11:47 -0700, Mahesh Bandewar wrote:
> > Yes functionally you will get the same result. However during the RX
> > processing, that code helps ipvlan-demux machine along with
> > packet-dispatcher to determine it early to drop the packet rather than
> > later.
> 
> When the interface is down, this doesn't matter, does it? You don't
> send/receive anything when the interface is down.

But obviously, with more ipvlan interfaces under the same master, some
of them being up and some down, it may be beneficial to keep the
addresses of interfaces that are down off the hash list. Which means my
original patch was correct after all...

Another question is whether the logic in ipvlan_addr_busy is correct.
To my understanding, the purpose of ipvlan_ht_addr_lookup call in
ipvlan_addr_busy is to ensure two interfaces under the same master
cannot have the same IP address assigned. As assigned addresses may not
be on the hash list when an interface is down, this check does not
really work. Note that this problem is already present in the current
code, with or without any patches currently discussed.

 Jiri

-- 
Jiri Benc

  reply	other threads:[~2015-03-25 23:49 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-23 21:10 [PATCH net] ipvlan: fix addr hash list corruption Jiri Benc
2015-03-24  1:10 ` Mahesh Bandewar
2015-03-24  8:58   ` Jiri Benc
2015-03-24 17:00 ` David Miller
2015-03-24 17:06   ` Jiri Benc
2015-03-24 23:16     ` Mahesh Bandewar
2015-03-25  1:18       ` David Miller
2015-03-25  8:58       ` Jiri Benc
2015-03-25 15:46         ` David Miller
2015-03-25 18:11           ` Mahesh Bandewar
2015-03-25 18:47             ` Dan Williams
2015-03-25 23:21             ` Jiri Benc
2015-03-25 23:49               ` Jiri Benc [this message]
2015-03-26  2:15               ` Mahesh Bandewar
2015-03-26  8:45                 ` Jiri Benc
2015-03-27  5:00                   ` Mahesh Bandewar

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=20150326004910.1259bed5@griffin \
    --to=jbenc@redhat.com \
    --cc=davem@davemloft.net \
    --cc=dcbw@redhat.com \
    --cc=maheshb@google.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 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.