From: Or Gerlitz <or.gerlitz@gmail.com>
To: David Miller <davem@davemloft.net>
Cc: Or Gerlitz <ogerlitz@mellanox.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
Amir Vadai <amirv@mellanox.com>
Subject: Re: [PATCH net 0/3] mlx4 fixes
Date: Wed, 12 Mar 2014 22:25:16 +0200 [thread overview]
Message-ID: <CAJZOPZKg20NEcccq5FT4EM-c-7PEDp3veZk8cbfbPqKnhE2P_g@mail.gmail.com> (raw)
In-Reply-To: <20140312.161408.2149985285610209.davem@davemloft.net>
On Wed, Mar 12, 2014 at 10:14 PM, David Miller <davem@davemloft.net> wrote:
> From: Or Gerlitz <ogerlitz@mellanox.com>
> Date: Wed, 12 Mar 2014 17:16:29 +0200
>
>> These short series fixes two bugs related to the vxlan support and a
>> missing req module call for the IB driver which is needed to support
>> IB/RDMA over Ethernet.
>>
>> Pathes done over the net tree, commit dd38743 "vlan: Set correct
>> source MAC address with TX VLAN offload enabled"
>
> Series applied, thanks Or.
>
> I wonder though, if a MAC address change results in a VLAN steering
> rule insertion failure, won't we be left in an inconsistent state?
in that case non-VXLAN traffic will fly in OK, but not VXLAN traffic.
I don't think we want to close the shop when this happens but probably
print some warning or a like, will send a patch...
next prev parent reply other threads:[~2014-03-12 20:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-12 15:16 [PATCH net 0/3] mlx4 fixes Or Gerlitz
2014-03-12 15:16 ` [PATCH net 1/3] net/mlx4_core: Fix wrong dump of the vxlan offloads device capability Or Gerlitz
2014-03-12 15:16 ` [PATCH net 2/3] net/mlx4_en: Handle vxlan steering rules for mac address changes Or Gerlitz
2014-03-12 15:16 ` [PATCH net 3/3] net/mlx4_core: Load the IB driver when the device supports IBoE Or Gerlitz
2014-03-12 20:14 ` [PATCH net 0/3] mlx4 fixes David Miller
2014-03-12 20:25 ` Or Gerlitz [this message]
2014-03-13 11:10 ` Or Gerlitz
-- strict thread matches above, loose matches on Subject: below --
2012-10-25 11:12 Or Gerlitz
2012-10-26 7:34 ` David Miller
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=CAJZOPZKg20NEcccq5FT4EM-c-7PEDp3veZk8cbfbPqKnhE2P_g@mail.gmail.com \
--to=or.gerlitz@gmail.com \
--cc=amirv@mellanox.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=ogerlitz@mellanox.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;
as well as URLs for NNTP newsgroup(s).