[b/oracle][PATCH 0/3] linux-oracle: Use upstream approach to fix a race when hot adding a VF

classic Classic list List threaded Threaded
7 messages Options
Reply | Threaded
Open this post in threaded view
|

[b/oracle][PATCH 0/3] linux-oracle: Use upstream approach to fix a race when hot adding a VF

Marcelo Henrique Cerri
BugLink: http://bugs.launchpad.net/bugs/1825229

I have provided a test kernel for the users, and they have provided a
positive feedback.

Daniel Borkmann (1):
  ipvlan, l3mdev: fix broken l3s mode wrt local routes

Marcelo Henrique Cerri (1):
  Revert "UBUNTU: SAUCE: net_failover: delay taking over primary device
    to accommodate udevd renaming"

Si-Wei Liu (1):
  UBUNTU: SAUCE: failover: allow name change on IFF_UP slave interfaces

 drivers/net/ipvlan/ipvlan_main.c |  6 +--
 drivers/net/net_failover.c       | 73 ++++----------------------------
 include/linux/netdevice.h        | 11 +++++
 include/net/l3mdev.h             |  3 +-
 include/net/net_failover.h       |  6 ---
 net/core/dev.c                   | 16 ++++++-
 net/core/failover.c              |  6 +--
 7 files changed, 42 insertions(+), 79 deletions(-)

--
2.20.1


--
kernel-team mailing list
[hidden email]
https://lists.ubuntu.com/mailman/listinfo/kernel-team
Reply | Threaded
Open this post in threaded view
|

[b/oracle][PATCH 1/3] Revert "UBUNTU: SAUCE: net_failover: delay taking over primary device to accommodate udevd renaming"

Marcelo Henrique Cerri
BugLink: http://bugs.launchpad.net/bugs/1825229

This reverts commit 6f89769c2772ccdf10bff4da1c3f3f3fbe551ed8.

Signed-off-by: Marcelo Henrique Cerri <[hidden email]>
---
 drivers/net/net_failover.c | 73 +++++---------------------------------
 include/net/net_failover.h |  6 ----
 2 files changed, 8 insertions(+), 71 deletions(-)

diff --git a/drivers/net/net_failover.c b/drivers/net/net_failover.c
index eeeed475a6a5..4f390fa557e4 100644
--- a/drivers/net/net_failover.c
+++ b/drivers/net/net_failover.c
@@ -28,10 +28,6 @@
 #include <uapi/linux/if_arp.h>
 #include <net/net_failover.h>
 
-#define TAKEOVER_DELAY_DEFAULT 100
-static unsigned long takeover_delay = TAKEOVER_DELAY_DEFAULT;
-module_param(takeover_delay, ulong, 0000);
-
 static bool net_failover_xmit_ready(struct net_device *dev)
 {
  return netif_running(dev) && netif_carrier_ok(dev);
@@ -505,7 +501,6 @@ static int net_failover_slave_register(struct net_device *slave_dev,
 {
  struct net_device *standby_dev, *primary_dev;
  struct net_failover_info *nfo_info;
- bool work_scheduled = false;
  bool slave_is_standby;
  u32 orig_mtu;
  int err;
@@ -521,21 +516,12 @@ static int net_failover_slave_register(struct net_device *slave_dev,
 
  dev_hold(slave_dev);
 
- slave_is_standby = slave_dev->dev.parent == failover_dev->dev.parent;
- nfo_info = netdev_priv(failover_dev);
-
  if (netif_running(failover_dev)) {
- if (takeover_delay && !slave_is_standby) {
- schedule_delayed_work(&nfo_info->takeover,
-      takeover_delay * HZ / 1000);
- work_scheduled = true;
- } else {
- err = dev_open(slave_dev);
- if (err && (err != -EBUSY)) {
- netdev_err(failover_dev, "Opening slave %s failed err:%d\n",
-   slave_dev->name, err);
- goto err_dev_open;
- }
+ err = dev_open(slave_dev);
+ if (err && (err != -EBUSY)) {
+ netdev_err(failover_dev, "Opening slave %s failed err:%d\n",
+   slave_dev->name, err);
+ goto err_dev_open;
  }
  }
 
@@ -548,13 +534,13 @@ static int net_failover_slave_register(struct net_device *slave_dev,
  if (err) {
  netdev_err(failover_dev, "Failed to add vlan ids to device %s err:%d\n",
    slave_dev->name, err);
- if (work_scheduled)
- cancel_delayed_work(&nfo_info->takeover);
  goto err_vlan_add;
  }
 
+ nfo_info = netdev_priv(failover_dev);
  standby_dev = rtnl_dereference(nfo_info->standby_dev);
  primary_dev = rtnl_dereference(nfo_info->primary_dev);
+ slave_is_standby = slave_dev->dev.parent == failover_dev->dev.parent;
 
  if (slave_is_standby) {
  rcu_assign_pointer(nfo_info->standby_dev, slave_dev);
@@ -691,48 +677,11 @@ static int net_failover_slave_name_change(struct net_device *slave_dev,
  /* We need to bring up the slave after the rename by udev in case
  * open failed with EBUSY when it was registered.
  */
- if (netif_running(failover_dev)) {
- dev_open(slave_dev);
-
- net_failover_lower_state_changed(slave_dev,
- primary_dev, standby_dev);
- }
+ dev_open(slave_dev);
 
  return 0;
 }
 
-static void net_failover_takeover_primary(struct work_struct *w)
-{
- struct net_failover_info *nfo_info
- = container_of(w, struct net_failover_info, takeover.work);
- struct net_device *primary_dev, *standby_dev;
- struct net_device *failover_dev;
- int err;
-
- if (!rtnl_trylock()) {
- schedule_delayed_work(&nfo_info->takeover, 0);
- return;
- }
-
- failover_dev = nfo_info->failover_dev;
- primary_dev = rtnl_dereference(nfo_info->primary_dev);
- standby_dev = rtnl_dereference(nfo_info->standby_dev);
-
- if (primary_dev && netif_running(failover_dev)) {
- err = dev_open(primary_dev);
- if (err) {
- netdev_err(failover_dev, "Opening primary %s failed err:%d\n",
-   primary_dev->name, err);
- } else {
- net_failover_lower_state_changed(primary_dev,
- primary_dev,
- standby_dev);
- }
- }
-
- rtnl_unlock();
-}
-
 static struct failover_ops net_failover_ops = {
  .slave_pre_register = net_failover_slave_pre_register,
  .slave_register = net_failover_slave_register,
@@ -759,7 +708,6 @@ static struct failover_ops net_failover_ops = {
 struct failover *net_failover_create(struct net_device *standby_dev)
 {
  struct device *dev = standby_dev->dev.parent;
- struct net_failover_info *nfo_info;
  struct net_device *failover_dev;
  struct failover *failover;
  int err;
@@ -811,9 +759,6 @@ struct failover *net_failover_create(struct net_device *standby_dev)
  }
 
  netif_carrier_off(failover_dev);
- nfo_info = netdev_priv(failover_dev);
- nfo_info->failover_dev = failover_dev;
- INIT_DELAYED_WORK(&nfo_info->takeover, net_failover_takeover_primary);
 
  failover = failover_register(failover_dev, &net_failover_ops);
  if (IS_ERR(failover))
@@ -853,8 +798,6 @@ void net_failover_destroy(struct failover *failover)
  failover_dev = rcu_dereference(failover->failover_dev);
  nfo_info = netdev_priv(failover_dev);
 
- cancel_delayed_work_sync(&nfo_info->takeover);
-
  netif_device_detach(failover_dev);
 
  rtnl_lock();
diff --git a/include/net/net_failover.h b/include/net/net_failover.h
index 3cd0a6142b2b..b12a1c469d1c 100644
--- a/include/net/net_failover.h
+++ b/include/net/net_failover.h
@@ -25,12 +25,6 @@ struct net_failover_info {
 
  /* spinlock while updating stats */
  spinlock_t stats_lock;
-
- /* back reference to associated net_device */
- struct net_device *failover_dev;
-
- /* delayed work to take over primary netdev */
- struct delayed_work takeover;
 };
 
 struct failover *net_failover_create(struct net_device *standby_dev);
--
2.20.1


--
kernel-team mailing list
[hidden email]
https://lists.ubuntu.com/mailman/listinfo/kernel-team
Reply | Threaded
Open this post in threaded view
|

[b/oracle][PATCH 2/3] ipvlan, l3mdev: fix broken l3s mode wrt local routes

Marcelo Henrique Cerri
In reply to this post by Marcelo Henrique Cerri
From: Daniel Borkmann <[hidden email]>

BugLink: http://bugs.launchpad.net/bugs/1825229

While implementing ipvlan l3 and l3s mode for kubernetes CNI plugin,
I ran into the issue that while l3 mode is working fine, l3s mode
does not have any connectivity to kube-apiserver and hence all pods
end up in Error state as well. The ipvlan master device sits on
top of a bond device and hostns traffic to kube-apiserver (also running
in hostns) is DNATed from 10.152.183.1:443 to 139.178.29.207:37573
where the latter is the address of the bond0. While in l3 mode, a
curl to https://10.152.183.1:443 or to https://139.178.29.207:37573
works fine from hostns, neither of them do in case of l3s. In the
latter only a curl to https://127.0.0.1:37573 appeared to work where
for local addresses of bond0 I saw kernel suddenly starting to emit
ARP requests to query HW address of bond0 which remained unanswered
and neighbor entries in INCOMPLETE state. These ARP requests only
happen while in l3s.

Debugging this further, I found the issue is that l3s mode is piggy-
backing on l3 master device, and in this case local routes are using
l3mdev_master_dev_rcu(dev) instead of net->loopback_dev as per commit
f5a0aab84b74 ("net: ipv4: dst for local input routes should use l3mdev
if relevant") and 5f02ce24c269 ("net: l3mdev: Allow the l3mdev to be
a loopback"). I found that reverting them back into using the
net->loopback_dev fixed ipvlan l3s connectivity and got everything
working for the CNI.

Now judging from 4fbae7d83c98 ("ipvlan: Introduce l3s mode") and the
l3mdev paper in [0] the only sole reason why ipvlan l3s is relying
on l3 master device is to get the l3mdev_ip_rcv() receive hook for
setting the dst entry of the input route without adding its own
ipvlan specific hacks into the receive path, however, any l3 domain
semantics beyond just that are breaking l3s operation. Note that
ipvlan also has the ability to dynamically switch its internal
operation from l3 to l3s for all ports via ipvlan_set_port_mode()
at runtime. In any case, l3 vs l3s soley distinguishes itself by
'de-confusing' netfilter through switching skb->dev to ipvlan slave
device late in NF_INET_LOCAL_IN before handing the skb to L4.

Minimal fix taken here is to add a IFF_L3MDEV_RX_HANDLER flag which,
if set from ipvlan setup, gets us only the wanted l3mdev_l3_rcv() hook
without any additional l3mdev semantics on top. This should also have
minimal impact since dev->priv_flags is already hot in cache. With
this set, l3s mode is working fine and I also get things like
masquerading pod traffic on the ipvlan master properly working.

  [0] https://netdevconf.org/1.2/papers/ahern-what-is-l3mdev-paper.pdf

Fixes: f5a0aab84b74 ("net: ipv4: dst for local input routes should use l3mdev if relevant")
Fixes: 5f02ce24c269 ("net: l3mdev: Allow the l3mdev to be a loopback")
Fixes: 4fbae7d83c98 ("ipvlan: Introduce l3s mode")
Signed-off-by: Daniel Borkmann <[hidden email]>
Cc: Mahesh Bandewar <[hidden email]>
Cc: David Ahern <[hidden email]>
Cc: Florian Westphal <[hidden email]>
Cc: Martynas Pumputis <[hidden email]>
Acked-by: David Ahern <[hidden email]>
Signed-off-by: David S. Miller <[hidden email]>
(cherry picked from commit d5256083f62e2720f75bb3c5a928a0afe47d6bc3)
[marcelo.cerri: commit added just as context for 8065a779f17e]
Signed-off-by: Marcelo Henrique Cerri <[hidden email]>
---
 drivers/net/ipvlan/ipvlan_main.c | 6 +++---
 include/linux/netdevice.h        | 8 ++++++++
 include/net/l3mdev.h             | 3 ++-
 3 files changed, 13 insertions(+), 4 deletions(-)

diff --git a/drivers/net/ipvlan/ipvlan_main.c b/drivers/net/ipvlan/ipvlan_main.c
index 00bc3a866b89..2bd7481119b0 100644
--- a/drivers/net/ipvlan/ipvlan_main.c
+++ b/drivers/net/ipvlan/ipvlan_main.c
@@ -84,12 +84,12 @@ static int ipvlan_set_port_mode(struct ipvl_port *port, u16 nval)
  err = ipvlan_register_nf_hook(read_pnet(&port->pnet));
  if (!err) {
  mdev->l3mdev_ops = &ipvl_l3mdev_ops;
- mdev->priv_flags |= IFF_L3MDEV_MASTER;
+ mdev->priv_flags |= IFF_L3MDEV_RX_HANDLER;
  } else
  return err;
  } else if (port->mode == IPVLAN_MODE_L3S) {
  /* Old mode was L3S */
- mdev->priv_flags &= ~IFF_L3MDEV_MASTER;
+ mdev->priv_flags &= ~IFF_L3MDEV_RX_HANDLER;
  ipvlan_unregister_nf_hook(read_pnet(&port->pnet));
  mdev->l3mdev_ops = NULL;
  }
@@ -142,7 +142,7 @@ static void ipvlan_port_destroy(struct net_device *dev)
  struct sk_buff *skb;
 
  if (port->mode == IPVLAN_MODE_L3S) {
- dev->priv_flags &= ~IFF_L3MDEV_MASTER;
+ dev->priv_flags &= ~IFF_L3MDEV_RX_HANDLER;
  ipvlan_unregister_nf_hook(dev_net(dev));
  dev->l3mdev_ops = NULL;
  }
diff --git a/include/linux/netdevice.h b/include/linux/netdevice.h
index a6cedb950a6c..cda67002cf1a 100644
--- a/include/linux/netdevice.h
+++ b/include/linux/netdevice.h
@@ -1381,6 +1381,7 @@ struct net_device_ops {
  * @IFF_NO_RX_HANDLER: device doesn't support the rx_handler hook
  * @IFF_FAILOVER: device is a failover master device
  * @IFF_FAILOVER_SLAVE: device is lower dev of a failover master device
+ * @IFF_L3MDEV_RX_HANDLER: only invoke the rx handler of L3 master device
  */
 enum netdev_priv_flags {
  IFF_802_1Q_VLAN = 1<<0,
@@ -1412,6 +1413,7 @@ enum netdev_priv_flags {
  IFF_NO_RX_HANDLER = 1<<26,
  IFF_FAILOVER = 1<<27,
  IFF_FAILOVER_SLAVE = 1<<28,
+ IFF_L3MDEV_RX_HANDLER = 1<<29,
 };
 
 #define IFF_802_1Q_VLAN IFF_802_1Q_VLAN
@@ -1442,6 +1444,7 @@ enum netdev_priv_flags {
 #define IFF_NO_RX_HANDLER IFF_NO_RX_HANDLER
 #define IFF_FAILOVER IFF_FAILOVER
 #define IFF_FAILOVER_SLAVE IFF_FAILOVER_SLAVE
+#define IFF_L3MDEV_RX_HANDLER IFF_L3MDEV_RX_HANDLER
 
 /**
  * struct net_device - The DEVICE structure.
@@ -4233,6 +4236,11 @@ static inline bool netif_supports_nofcs(struct net_device *dev)
  return dev->priv_flags & IFF_SUPP_NOFCS;
 }
 
+static inline bool netif_has_l3_rx_handler(const struct net_device *dev)
+{
+ return dev->priv_flags & IFF_L3MDEV_RX_HANDLER;
+}
+
 static inline bool netif_is_l3_master(const struct net_device *dev)
 {
  return dev->priv_flags & IFF_L3MDEV_MASTER;
diff --git a/include/net/l3mdev.h b/include/net/l3mdev.h
index 3832099289c5..128487658ff7 100644
--- a/include/net/l3mdev.h
+++ b/include/net/l3mdev.h
@@ -142,7 +142,8 @@ struct sk_buff *l3mdev_l3_rcv(struct sk_buff *skb, u16 proto)
 
  if (netif_is_l3_slave(skb->dev))
  master = netdev_master_upper_dev_get_rcu(skb->dev);
- else if (netif_is_l3_master(skb->dev))
+ else if (netif_is_l3_master(skb->dev) ||
+ netif_has_l3_rx_handler(skb->dev))
  master = skb->dev;
 
  if (master && master->l3mdev_ops->l3mdev_l3_rcv)
--
2.20.1


--
kernel-team mailing list
[hidden email]
https://lists.ubuntu.com/mailman/listinfo/kernel-team
Reply | Threaded
Open this post in threaded view
|

[b/oracle][PATCH 3/3] UBUNTU: SAUCE: failover: allow name change on IFF_UP slave interfaces

Marcelo Henrique Cerri
In reply to this post by Marcelo Henrique Cerri
From: Si-Wei Liu <[hidden email]>

BugLink: http://bugs.launchpad.net/bugs/1825229

When a netdev appears through hot plug then gets enslaved by a failover
master that is already up and running, the slave will be opened
right away after getting enslaved. Today there's a race that userspace
(udev) may fail to rename the slave if the kernel (net_failover)
opens the slave earlier than when the userspace rename happens.
Unlike bond or team, the primary slave of failover can't be renamed by
userspace ahead of time, since the kernel initiated auto-enslavement is
unable to, or rather, is never meant to be synchronized with the rename
request from userspace.

As the failover slave interfaces are not designed to be operated
directly by userspace apps: IP configuration, filter rules with
regard to network traffic passing and etc., should all be done on master
interface. In general, userspace apps only care about the
name of master interface, while slave names are less important as long
as admin users can see reliable names that may carry
other information describing the netdev. For e.g., they can infer that
"ens3nsby" is a standby slave of "ens3", while for a
name like "eth0" they can't tell which master it belongs to.

Historically the name of IFF_UP interface can't be changed because
there might be admin script or management software that is already
relying on such behavior and assumes that the slave name can't be
changed once UP. But failover is special: with the in-kernel
auto-enslavement mechanism, the userspace expectation for device
enumeration and bring-up order is already broken. Previously initramfs
and various userspace config tools were modified to bypass failover
slaves because of auto-enslavement and duplicate MAC address. Similarly,
in case that users care about seeing reliable slave name, the new type
of failover slaves needs to be taken care of specifically in userspace
anyway.

It's less risky to lift up the rename restriction on failover slave
which is already UP. Although it's possible this change may potentially
break userspace component (most likely configuration scripts or
management software) that assumes slave name can't be changed while
UP, it's relatively a limited and controllable set among all userspace
components, which can be fixed specifically to listen for the rename
events on failover slaves. Userspace component interacting with slaves
is expected to be changed to operate on failover master interface
instead, as the failover slave is dynamic in nature which may come and
go at any point.  The goal is to make the role of failover slaves less
relevant, and userspace components should only deal with failover master
in the long run.

Fixes: 30c8bd5aa8b2 ("net: Introduce generic failover module")
Signed-off-by: Si-Wei Liu <[hidden email]>
Reviewed-by: Liran Alon <[hidden email]>
Acked-by: Sridhar Samudrala <[hidden email]>
Signed-off-by: David S. Miller <[hidden email]>
(cherry picked from commit 8065a779f17e94536a1c4dcee4f9d88011672f97)
[marcelo.cerri: picked from git://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git]
Signed-off-by: Marcelo Henrique Cerri <[hidden email]>
---
 include/linux/netdevice.h |  3 +++
 net/core/dev.c            | 16 +++++++++++++++-
 net/core/failover.c       |  6 +++---
 3 files changed, 21 insertions(+), 4 deletions(-)

diff --git a/include/linux/netdevice.h b/include/linux/netdevice.h
index cda67002cf1a..3343b48e8737 100644
--- a/include/linux/netdevice.h
+++ b/include/linux/netdevice.h
@@ -1382,6 +1382,7 @@ struct net_device_ops {
  * @IFF_FAILOVER: device is a failover master device
  * @IFF_FAILOVER_SLAVE: device is lower dev of a failover master device
  * @IFF_L3MDEV_RX_HANDLER: only invoke the rx handler of L3 master device
+ * @IFF_LIVE_RENAME_OK: rename is allowed while device is up and running
  */
 enum netdev_priv_flags {
  IFF_802_1Q_VLAN = 1<<0,
@@ -1414,6 +1415,7 @@ enum netdev_priv_flags {
  IFF_FAILOVER = 1<<27,
  IFF_FAILOVER_SLAVE = 1<<28,
  IFF_L3MDEV_RX_HANDLER = 1<<29,
+ IFF_LIVE_RENAME_OK = 1<<30,
 };
 
 #define IFF_802_1Q_VLAN IFF_802_1Q_VLAN
@@ -1445,6 +1447,7 @@ enum netdev_priv_flags {
 #define IFF_FAILOVER IFF_FAILOVER
 #define IFF_FAILOVER_SLAVE IFF_FAILOVER_SLAVE
 #define IFF_L3MDEV_RX_HANDLER IFF_L3MDEV_RX_HANDLER
+#define IFF_LIVE_RENAME_OK IFF_LIVE_RENAME_OK
 
 /**
  * struct net_device - The DEVICE structure.
diff --git a/net/core/dev.c b/net/core/dev.c
index ea49a28976a8..58e69a24a234 100644
--- a/net/core/dev.c
+++ b/net/core/dev.c
@@ -1182,7 +1182,21 @@ int dev_change_name(struct net_device *dev, const char *newname)
  BUG_ON(!dev_net(dev));
 
  net = dev_net(dev);
- if (dev->flags & IFF_UP)
+
+ /* Some auto-enslaved devices e.g. failover slaves are
+ * special, as userspace might rename the device after
+ * the interface had been brought up and running since
+ * the point kernel initiated auto-enslavement. Allow
+ * live name change even when these slave devices are
+ * up and running.
+ *
+ * Typically, users of these auto-enslaving devices
+ * don't actually care about slave name change, as
+ * they are supposed to operate on master interface
+ * directly.
+ */
+ if (dev->flags & IFF_UP &&
+    likely(!(dev->priv_flags & IFF_LIVE_RENAME_OK)))
  return -EBUSY;
 
  write_seqcount_begin(&devnet_rename_seq);
diff --git a/net/core/failover.c b/net/core/failover.c
index 4a92a98ccce9..b5cd3c727285 100644
--- a/net/core/failover.c
+++ b/net/core/failover.c
@@ -80,14 +80,14 @@ static int failover_slave_register(struct net_device *slave_dev)
  goto err_upper_link;
  }
 
- slave_dev->priv_flags |= IFF_FAILOVER_SLAVE;
+ slave_dev->priv_flags |= (IFF_FAILOVER_SLAVE | IFF_LIVE_RENAME_OK);
 
  if (fops && fops->slave_register &&
     !fops->slave_register(slave_dev, failover_dev))
  return NOTIFY_OK;
 
  netdev_upper_dev_unlink(slave_dev, failover_dev);
- slave_dev->priv_flags &= ~IFF_FAILOVER_SLAVE;
+ slave_dev->priv_flags &= ~(IFF_FAILOVER_SLAVE | IFF_LIVE_RENAME_OK);
 err_upper_link:
  netdev_rx_handler_unregister(slave_dev);
 done:
@@ -121,7 +121,7 @@ int failover_slave_unregister(struct net_device *slave_dev)
 
  netdev_rx_handler_unregister(slave_dev);
  netdev_upper_dev_unlink(slave_dev, failover_dev);
- slave_dev->priv_flags &= ~IFF_FAILOVER_SLAVE;
+ slave_dev->priv_flags &= ~(IFF_FAILOVER_SLAVE | IFF_LIVE_RENAME_OK);
 
  if (fops && fops->slave_unregister &&
     !fops->slave_unregister(slave_dev, failover_dev))
--
2.20.1


--
kernel-team mailing list
[hidden email]
https://lists.ubuntu.com/mailman/listinfo/kernel-team
Reply | Threaded
Open this post in threaded view
|

ACK: [b/oracle][PATCH 0/3] linux-oracle: Use upstream approach to fix a race when hot adding a VF

Seth Forshee
In reply to this post by Marcelo Henrique Cerri
On Mon, Apr 22, 2019 at 09:43:44AM -0300, Marcelo Henrique Cerri wrote:
> BugLink: http://bugs.launchpad.net/bugs/1825229
>
> I have provided a test kernel for the users, and they have provided a
> positive feedback.

Trading a sauce patch for upstream cherry picks, positive testing.

Acked-by: Seth Forshee <[hidden email]>

--
kernel-team mailing list
[hidden email]
https://lists.ubuntu.com/mailman/listinfo/kernel-team
Reply | Threaded
Open this post in threaded view
|

ACK: [b/oracle][PATCH 0/3] linux-oracle: Use upstream approach to fix a race when hot adding a VF

Thadeu Lima de Souza Cascardo-3
In reply to this post by Marcelo Henrique Cerri
Restricted to linux-oracle, nice upstream cherry picks.

Acked-by: Thadeu Lima de Souza Cascardo <[hidden email]>

--
kernel-team mailing list
[hidden email]
https://lists.ubuntu.com/mailman/listinfo/kernel-team
Reply | Threaded
Open this post in threaded view
|

APPLIED: [b/oracle][PATCH 0/3] linux-oracle: Use upstream approach to fix a race when hot adding a VF

Marcelo Henrique Cerri
In reply to this post by Marcelo Henrique Cerri
--
kernel-team mailing list
[hidden email]
https://lists.ubuntu.com/mailman/listinfo/kernel-team

signature.asc (499 bytes) Download Attachment