All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mahesh Bandewar <maheshb@google.com>
To: David Miller <davem@davemloft.net>
Cc: jbenc@redhat.com, linux-netdev <netdev@vger.kernel.org>, dcbw@redhat.com
Subject: Re: [PATCH net] ipvlan: fix addr hash list corruption
Date: Wed, 25 Mar 2015 11:11:47 -0700	[thread overview]
Message-ID: <CAF2d9jh5WaNYsMxp29GY3LqM08jjVPwLd1BQ1HLFKMsKFda6zQ@mail.gmail.com> (raw)
In-Reply-To: <20150325.114622.1915164845375005128.davem@davemloft.net>

On Wed, Mar 25, 2015 at 8:46 AM, David Miller <davem@davemloft.net> wrote:
> From: Jiri Benc <jbenc@redhat.com>
> Date: Wed, 25 Mar 2015 09:58:51 +0100
>
>> On Tue, 24 Mar 2015 16:16:38 -0700, Mahesh Bandewar wrote:
>>> Well, we already have hlist_unhashed().The following patch should fix
>>> the duplicate addition as well as deletion. Please give it a try.
>>
>> Good idea, it's surely better than adding a new boolean.
>>
>> However, I'm wondering that when there's apparently no problem with the
>> addresses being on the hash list when interface is down, what's the
>> point in clearing the hash list in the ndo_stop handler and
>> repopulating it in ndo_open?
>>
>> The following patch fixes the problem, too, and as a bonus removes code:
>
> I'll let Mahesh reply to this.

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. Also note that addition / deletion of address entries in
hash-table is done in control-path while the demux / dispatcher
operate in data-path. So for this reason I would prefer to leave the
hash-table entries addition / deletion as it is.

--mahesh..

  reply	other threads:[~2015-03-25 18:12 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 [this message]
2015-03-25 18:47             ` Dan Williams
2015-03-25 23:21             ` Jiri Benc
2015-03-25 23:49               ` Jiri Benc
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=CAF2d9jh5WaNYsMxp29GY3LqM08jjVPwLd1BQ1HLFKMsKFda6zQ@mail.gmail.com \
    --to=maheshb@google.com \
    --cc=davem@davemloft.net \
    --cc=dcbw@redhat.com \
    --cc=jbenc@redhat.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.