From: David Miller <davem@davemloft.net>
To: idosch@mellanox.com
Cc: netdev@vger.kernel.org, jiri@mellanox.com, nird@mellanox.com,
petrm@mellanox.com
Subject: Re: [PATCH net 0/4] mlxsw: Various fixes
Date: Thu, 06 Dec 2018 13:31:44 -0800 (PST) [thread overview]
Message-ID: <20181206.133144.86747183529291081.davem@davemloft.net> (raw)
In-Reply-To: <20181206174427.4952-1-idosch@mellanox.com>
From: Ido Schimmel <idosch@mellanox.com>
Date: Thu, 6 Dec 2018 17:44:48 +0000
> Patches #1 and #2 fix two VxLAN related issues. The first patch removes
> warnings that can currently be triggered from user space. Second patch
> avoids leaking a FID in an error path.
>
> Patch #3 fixes a too strict check that causes certain host routes not to
> be promoted to perform GRE decapsulation in hardware.
>
> Last patch avoids a use-after-free when deleting a VLAN device via an
> ioctl when it is enslaved to a bridge. I have a patchset for net-next
> that reworks this code and makes the driver more robust.
Series applied.
next prev parent reply other threads:[~2018-12-06 21:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-06 17:44 [PATCH net 0/4] mlxsw: Various fixes Ido Schimmel
2018-12-06 17:44 ` [PATCH net 1/4] mlxsw: spectrum_nve: Remove easily triggerable warnings Ido Schimmel
2018-12-06 17:44 ` [PATCH net 2/4] mlxsw: spectrum_switchdev: Avoid leaking FID's reference count Ido Schimmel
2018-12-06 17:44 ` [PATCH net 3/4] mlxsw: spectrum_router: Relax GRE decap matching check Ido Schimmel
2018-12-06 17:44 ` [PATCH net 4/4] mlxsw: spectrum_switchdev: Fix VLAN device deletion via ioctl Ido Schimmel
2018-12-06 21:31 ` David Miller [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-01-12 16:06 [PATCH net 0/4] mlxsw: Various fixes Ido Schimmel
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=20181206.133144.86747183529291081.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=idosch@mellanox.com \
--cc=jiri@mellanox.com \
--cc=netdev@vger.kernel.org \
--cc=nird@mellanox.com \
--cc=petrm@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).