Seeing WARN_ON in ib_dealloc_pd from ipoib in kernel 4.3-rc1-debug

DISCUSSION Sagi Grimberg 5 participants 8 messages Oct 7, 2015 – Oct 12, 2015 4 messages not in the archive InfiniBand

lore

Share & tools

lore

Sagi Grimberg

author

2015-10-07 15:51 UTC #0 lore raw

This started popping up (not sure if it's new to 4.3-rc1).

Happens when unloading the provider driver (mlx4/mlx5 in my case).

Has anyone seen this?

kernel: ------------[ cut here ]------------
kernel: WARNING: CPU: 2 PID: 6012 at drivers/infiniband/core/verbs.c:283 ib_dealloc_pd+0x5b/0xa0 [ib_core]()
kernel: Modules linked in: rpcrdma ib_srp scsi_transport_srp ib_iser rdma_cm iw_cm libiscsi scsi_transport_iscsi ib_umad ib_uverbs ib_ipoib ib_cm mlx4_ib ib_sa ib_mad mlx4_core mlx5_ib(-) mlx5_core ib_core ib_addr mst_pciconf(O) mst_pci(O) nfsv3 nfs af_packet coretemp x86_pkg_temp_thermal crct10dif_pclmul crc32c_intel aesni_intel aes_x86_64 glue_helper lrw gf128mul ablk_helper cryptd microcode ipmi_ssif pcspkr lpc_ich i2c_i801 mfd_core ioatdma wmi ipmi_si ipmi_msghandler processor button nfsd auth_rpcgss oid_registry nfs_acl lockd grace sunrpc ip_tables x_tables ext4 crc16 mbcache jbd2 sd_mod hid_generic usbhid hid ahci libahci libata igb ehci_pci hwmon ehci_hcd ptp usbcore pps_core scsi_mod i2c_algo_bit usb_common i2c_core dca autofs4 [last unloaded: mlx4_core]

kernel: CPU: 2 PID: 6012 Comm: modprobe Tainted: G           O L 4.3.0-rc3-debug+ #67
kernel: Hardware name: Supermicro SYS-1027R-WRF/X9DRW, BIOS 3.0a 08/08/2013
kernel:  000000000000011b ffff8807a99afbe8 ffffffff8129915b 0000000000000009
kernel:  0000000000000000 ffff8807a99afc28 ffffffff810752b5 ffff880827d7c2a0
kernel:  ffff8807b0d03260 ffff880827d7c2a0 ffff880827d7cc60 0000000000000000
kernel: Call Trace:
kernel:  [<ffffffff8129915b>] dump_stack+0x4f/0x74
kernel:  [<ffffffff810752b5>] warn_slowpath_common+0x95/0xe0
kernel:  [<ffffffff8107531a>] warn_slowpath_null+0x1a/0x20
kernel:  [<ffffffffa001bd4b>] ib_dealloc_pd+0x5b/0xa0 [ib_core]
kernel:  [<ffffffffa047adce>] ipoib_transport_dev_cleanup+0x9e/0xf0 [ib_ipoib]
kernel:  [<ffffffffa047712e>] ipoib_ib_dev_cleanup+0x5e/0x80 [ib_ipoib]
kernel:  [<ffffffffa0473984>] ipoib_dev_cleanup+0x2a4/0x3b0 [ib_ipoib]
kernel:  [<ffffffff8107a11d>] ? __local_bh_enable_ip+0x6d/0xd0
kernel:  [<ffffffffa0473a9e>] ipoib_uninit+0xe/0x10 [ib_ipoib]
kernel:  [<ffffffff8141ba17>] rollback_registered_many+0x1a7/0x2c0
kernel:  [<ffffffff8141bbd1>] rollback_registered+0x31/0x40
kernel:  [<ffffffff8141bc38>] unregister_netdevice_queue+0x58/0xb0
kernel:  [<ffffffff8141be00>] unregister_netdev+0x20/0x30
kernel:  [<ffffffffa04721a1>] ipoib_remove_one+0xa1/0xe0 [ib_ipoib]
kernel:  [<ffffffffa001e0d1>] ib_unregister_device+0xc1/0x160 [ib_core]
kernel:  [<ffffffffa05231f9>] mlx5_ib_remove+0x19/0x50 [mlx5_ib]
kernel:  [<ffffffffa04e5068>] mlx5_remove_device+0x68/0x80 [mlx5_core]
kernel:  [<ffffffffa04e50be>] mlx5_unregister_interface+0x3e/0x70 [mlx5_core]
kernel:  [<ffffffffa053397c>] mlx5_ib_cleanup+0x10/0x694 [mlx5_ib]
kernel:  [<ffffffff810f67aa>] SyS_delete_module+0x17a/0x1c0
kernel:  [<ffffffff81003017>] ? trace_hardirqs_on_thunk+0x17/0x19
kernel:  [<ffffffff811e80b0>] ? generic_show_options+0x180/0x180
kernel:  [<ffffffff8151a1f2>] entry_SYSCALL_64_fastpath+0x12/0x76
kernel: ---[ end trace 31339c7283574ccb ]---

--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html

A message that is not in the archive (sent off-list or not yet received): 56153F71.2010801-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org

Doug Ledford

2015-10-07 16:11 UTC #2 lore raw

Quoted 49 lines · Sagi Grimberg

This started popping up (not sure if it's new to 4.3-rc1).
Happens when unloading the provider driver (mlx4/mlx5 in my case).
Has anyone seen this?
kernel: ------------[ cut here ]------------
kernel: WARNING: CPU: 2 PID: 6012 at drivers/infiniband/core/verbs.c:283 ib_dealloc_pd+0x5b/0xa0 [ib_core]()
kernel: Modules linked in: rpcrdma ib_srp scsi_transport_srp ib_iser rdma_cm iw_cm libiscsi scsi_transport_iscsi ib_umad ib_uverbs ib_ipoib ib_cm mlx4_ib ib_sa ib_mad mlx4_core mlx5_ib(-) mlx5_core ib_core ib_addr mst_pciconf(O) mst_pci(O) nfsv3 nfs af_packet coretemp x86_pkg_temp_thermal crct10dif_pclmul crc32c_intel aesni_intel aes_x86_64 glue_helper lrw gf128mul ablk_helper cryptd microcode ipmi_ssif pcspkr lpc_ich i2c_i801 mfd_core ioatdma wmi ipmi_si ipmi_msghandler processor button nfsd auth_rpcgss oid_registry nfs_acl lockd grace sunrpc ip_tables x_tables ext4 crc16 mbcache jbd2 sd_mod hid_generic usbhid hid ahci libahci libata igb ehci_pci hwmon ehci_hcd ptp usbcore pps_core scsi_mod i2c_algo_bit usb_common i2c_core dca autofs4 [last unloaded: mlx4_core]
kernel: CPU: 2 PID: 6012 Comm: modprobe Tainted: G O L
4.3.0-rc3-debug+ #67
kernel: Hardware name: Supermicro SYS-1027R-WRF/X9DRW, BIOS 3.0a 08/08/2013
kernel: 000000000000011b ffff8807a99afbe8 ffffffff8129915b 0000000000000009
kernel: 0000000000000000 ffff8807a99afc28 ffffffff810752b5 ffff880827d7c2a0
kernel: ffff8807b0d03260 ffff880827d7c2a0 ffff880827d7cc60 0000000000000000
kernel: Call Trace:
kernel:  [<ffffffff8129915b>] dump_stack+0x4f/0x74
kernel:  [<ffffffff810752b5>] warn_slowpath_common+0x95/0xe0
kernel:  [<ffffffff8107531a>] warn_slowpath_null+0x1a/0x20
kernel:  [<ffffffffa001bd4b>] ib_dealloc_pd+0x5b/0xa0 [ib_core]
kernel:  [<ffffffffa047adce>] ipoib_transport_dev_cleanup+0x9e/0xf0
[ib_ipoib]
kernel:  [<ffffffffa047712e>] ipoib_ib_dev_cleanup+0x5e/0x80 [ib_ipoib]
kernel:  [<ffffffffa0473984>] ipoib_dev_cleanup+0x2a4/0x3b0 [ib_ipoib]
kernel:  [<ffffffff8107a11d>] ? __local_bh_enable_ip+0x6d/0xd0
kernel:  [<ffffffffa0473a9e>] ipoib_uninit+0xe/0x10 [ib_ipoib]
kernel:  [<ffffffff8141ba17>] rollback_registered_many+0x1a7/0x2c0
kernel:  [<ffffffff8141bbd1>] rollback_registered+0x31/0x40
kernel:  [<ffffffff8141bc38>] unregister_netdevice_queue+0x58/0xb0
kernel:  [<ffffffff8141be00>] unregister_netdev+0x20/0x30
kernel:  [<ffffffffa04721a1>] ipoib_remove_one+0xa1/0xe0 [ib_ipoib]
kernel:  [<ffffffffa001e0d1>] ib_unregister_device+0xc1/0x160 [ib_core]
kernel:  [<ffffffffa05231f9>] mlx5_ib_remove+0x19/0x50 [mlx5_ib]
kernel:  [<ffffffffa04e5068>] mlx5_remove_device+0x68/0x80 [mlx5_core]

Quoted 8 lines

kernel:  [<ffffffffa04e50be>] mlx5_unregister_interface+0x3e/0x70
[mlx5_core]
kernel:  [<ffffffffa053397c>] mlx5_ib_cleanup+0x10/0x694 [mlx5_ib]
kernel:  [<ffffffff810f67aa>] SyS_delete_module+0x17a/0x1c0
kernel:  [<ffffffff81003017>] ? trace_hardirqs_on_thunk+0x17/0x19
kernel:  [<ffffffff811e80b0>] ? generic_show_options+0x180/0x180
kernel:  [<ffffffff8151a1f2>] entry_SYSCALL_64_fastpath+0x12/0x76
kernel: ---[ end trace 31339c7283574ccb ]---

Yes. I'm seeing this too. The last time this popped up I fixed it by adding the code for reaping ahs. I suspect that the new code to timeout sendonly multicast joins combined with us now creating and joining what used to be sendonly groups is the likely culprit here.

Signature · 2 lines

Doug Ledford <[email protected]>
              GPG KeyID: 0E572FDD

A message that is not in the archive (sent off-list or not yet received): [email protected]

Sagi Grimberg

author

2015-10-11 15:51 UTC #4 lore raw

Quoted 6 lines

Yes. I'm seeing this too. The last time this popped up I fixed it by adding the code for reaping ahs. I suspect that the new code to timeout sendonly multicast joins combined with us now creating and joining what used to be sendonly groups is the likely culprit here.

Is someone looking at this? It really should be fixed before 4.3 final...
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html

A message that is not in the archive (sent off-list or not yet received): 561A8591.4020608-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org

Christoph Lameter

2015-10-11 23:49 UTC #6 lore raw

Quoted 2 lines · Sagi Grimberg

Is someone looking at this? It really should be fixed before 4.3 final...

The following fixup patch is needed:

Subject: ipoib: For sendonly join free the multicast group on leave

When we leave the multicast group on expiration of a neighbor we do not free the mcast structure. This results in a memory leak.

Signed-off-by Christoph Lameter <[email protected]>

drivers/infiniband/ulp/ipoib/ipoib.h +1 -0

Index: linux/drivers/infiniband/ulp/ipoib/ipoib.h
===================================================================
@@ -495,6 +495,7 @@ void ipoib_dev_cleanup(struct net_device
 void ipoib_mcast_join_task(struct work_struct *work);
 void ipoib_mcast_carrier_on_task(struct work_struct *work);
 void ipoib_mcast_send(struct net_device *dev, u8 *daddr, struct sk_buff *skb);
+void ipoib_mcast_free(struct ipoib_mcast *mc);
 
 void ipoib_mcast_restart_task(struct work_struct *work);
 int ipoib_mcast_start_thread(struct net_device *dev);

drivers/infiniband/ulp/ipoib/ipoib_main.c +3 -1

Index: linux/drivers/infiniband/ulp/ipoib/ipoib_main.c
===================================================================
@@ -1207,8 +1207,10 @@ static void __ipoib_reap_neigh(struct ip
 
 out_unlock:
 	spin_unlock_irqrestore(&priv->lock, flags);
-	list_for_each_entry_safe(mcast, tmcast, &remove_list, list)
+	list_for_each_entry_safe(mcast, tmcast, &remove_list, list) {
 		ipoib_mcast_leave(dev, mcast);
+		ipoib_mcast_free(mcast);
+	}
 }
 
 static void ipoib_reap_neigh(struct work_struct *work)

drivers/infiniband/ulp/ipoib/ipoib_multicast.c +1 -1

Index: linux/drivers/infiniband/ulp/ipoib/ipoib_multicast.c
===================================================================
@@ -106,7 +106,7 @@ static void __ipoib_mcast_schedule_join_
 		queue_delayed_work(priv->wq, &priv->mcast_task, 0);
 }
 
-static void ipoib_mcast_free(struct ipoib_mcast *mcast)
+void ipoib_mcast_free(struct ipoib_mcast *mcast)
 {
 	struct net_device *dev = mcast->dev;
 	int tx_dropped = 0;

--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html

A message that is not in the archive (sent off-list or not yet received): alpine.DEB.2.20.1510111848560.10812-wcBtFHqTun5QOdAKl3ChDw@public.gmane.org

Sagi Grimberg

author Tested-by

2015-10-12 07:53 UTC #8 lore raw

Quoted 46 lines

The following fixup patch is needed:
Subject: ipoib: For sendonly join free the multicast group on leave
When we leave the multicast group on expiration of a neighbor we do not free the mcast structure. This results in a memory leak.
Signed-off-by Christoph Lameter <[email protected]>
Index: linux/drivers/infiniband/ulp/ipoib/ipoib.h
===================================================================
drivers/infiniband/ulp/ipoib/ipoib.h +1 -0
@@ -495,6 +495,7 @@ void ipoib_dev_cleanup(struct net_device
  void ipoib_mcast_join_task(struct work_struct *work);
  void ipoib_mcast_carrier_on_task(struct work_struct *work);
  void ipoib_mcast_send(struct net_device *dev, u8 *daddr, struct sk_buff *skb);
+void ipoib_mcast_free(struct ipoib_mcast *mc);
 
  void ipoib_mcast_restart_task(struct work_struct *work);
  int ipoib_mcast_start_thread(struct net_device *dev);
Index: linux/drivers/infiniband/ulp/ipoib/ipoib_main.c
===================================================================
drivers/infiniband/ulp/ipoib/ipoib_main.c +3 -1
@@ -1207,8 +1207,10 @@ static void __ipoib_reap_neigh(struct ip
 
  out_unlock:
  	spin_unlock_irqrestore(&priv->lock, flags);
-	list_for_each_entry_safe(mcast, tmcast, &remove_list, list)
+	list_for_each_entry_safe(mcast, tmcast, &remove_list, list) {
  		ipoib_mcast_leave(dev, mcast);
+		ipoib_mcast_free(mcast);
+	}
  }
 
  static void ipoib_reap_neigh(struct work_struct *work)
Index: linux/drivers/infiniband/ulp/ipoib/ipoib_multicast.c
===================================================================

drivers/infiniband/ulp/ipoib/ipoib_multicast.c static void __ipoib_mcast_schedule_join_ · line 112

Quoted 8 lines

drivers/infiniband/ulp/ipoib/ipoib_multicast.c +1 -1

@@ -106,7 +106,7 @@ static void __ipoib_mcast_schedule_join_
  		queue_delayed_work(priv->wq, &priv->mcast_task, 0);
  }
 
-static void ipoib_mcast_free(struct ipoib_mcast *mcast)
+void ipoib_mcast_free(struct ipoib_mcast *mcast)
  {
  	struct net_device *dev = mcast->dev;
  	int tx_dropped = 0;

Hey Christoph,

Thanks for the quick patch. When you re-spin this as a proper patch you can add my:

Tested-by Sagi Grimberg <sagig-VPRAkNaXOzVWk0Htik3J/[email protected]>

--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html

Doug Ledford

2015-10-12 12:35 UTC #9 lore raw

In reply to a message not in the archive

Quoted 6 lines · Christoph Lameter

Quoted 2 lines · Sagi Grimberg
Is someone looking at this? It really should be fixed before 4.3 final...
The following fixup patch is needed:

Thanks Christoph. I figured the issue had to have come from the new code, but I hadn't had a chance to track it down yet.

Quoted 55 lines

Subject: ipoib: For sendonly join free the multicast group on leave
When we leave the multicast group on expiration of a neighbor we do not free the mcast structure. This results in a memory leak.
Signed-off-by Christoph Lameter <[email protected]>
Index: linux/drivers/infiniband/ulp/ipoib/ipoib.h
===================================================================
drivers/infiniband/ulp/ipoib/ipoib.h +1 -0
@@ -495,6 +495,7 @@ void ipoib_dev_cleanup(struct net_device
 void ipoib_mcast_join_task(struct work_struct *work);
 void ipoib_mcast_carrier_on_task(struct work_struct *work);
 void ipoib_mcast_send(struct net_device *dev, u8 *daddr, struct sk_buff *skb);
+void ipoib_mcast_free(struct ipoib_mcast *mc);
 
 void ipoib_mcast_restart_task(struct work_struct *work);
 int ipoib_mcast_start_thread(struct net_device *dev);
Index: linux/drivers/infiniband/ulp/ipoib/ipoib_main.c
===================================================================
drivers/infiniband/ulp/ipoib/ipoib_main.c +3 -1
@@ -1207,8 +1207,10 @@ static void __ipoib_reap_neigh(struct ip
 
 out_unlock:
 	spin_unlock_irqrestore(&priv->lock, flags);
-	list_for_each_entry_safe(mcast, tmcast, &remove_list, list)
+	list_for_each_entry_safe(mcast, tmcast, &remove_list, list) {
 		ipoib_mcast_leave(dev, mcast);
+		ipoib_mcast_free(mcast);
+	}
 }
 
 static void ipoib_reap_neigh(struct work_struct *work)
Index: linux/drivers/infiniband/ulp/ipoib/ipoib_multicast.c
===================================================================
drivers/infiniband/ulp/ipoib/ipoib_multicast.c +1 -2
@@ -106,7 +106,7 @@ static void __ipoib_mcast_schedule_join_
 		queue_delayed_work(priv->wq, &priv->mcast_task, 0);
 }
 
-static void ipoib_mcast_free(struct ipoib_mcast *mcast)
+void ipoib_mcast_free(struct ipoib_mcast *mcast)
 {
 	struct net_device *dev = mcast->dev;
 	int tx_dropped = 0;
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html

Signature · 2 lines

Doug Ledford <[email protected]>
              GPG KeyID: 0E572FDD

[email protected]

2015-10-07 16:22 UTC #10 lore raw

In reply to a message not in the archive

Sagi,

Quoted 6 lines · Sagi Grimberg

This started popping up (not sure if it's new to 4.3-rc1).
Happens when unloading the provider driver (mlx4/mlx5 in my case).
Has anyone seen this?

Not sure it is useful but yes I have seen similar dump with RDS on 4.3-rc1. I later found that RDS code had mr leak(s) in normal operation which lead to WARNS on module clean up. I believe the leaks lead to pd 'usecnt' getting messed up. Once i avoided that, I stopped seeing it.

Quoted 51 lines

kernel: ------------[ cut here ]------------
kernel: WARNING: CPU: 2 PID: 6012 at drivers/infiniband/core/verbs.c:283 ib_dealloc_pd+0x5b/0xa0 [ib_core]()
kernel: Modules linked in: rpcrdma ib_srp scsi_transport_srp ib_iser rdma_cm iw_cm libiscsi scsi_transport_iscsi ib_umad ib_uverbs ib_ipoib ib_cm mlx4_ib ib_sa ib_mad mlx4_core mlx5_ib(-) mlx5_core ib_core ib_addr mst_pciconf(O) mst_pci(O) nfsv3 nfs af_packet coretemp x86_pkg_temp_thermal crct10dif_pclmul crc32c_intel aesni_intel aes_x86_64 glue_helper lrw gf128mul ablk_helper cryptd microcode ipmi_ssif pcspkr lpc_ich i2c_i801 mfd_core ioatdma wmi ipmi_si ipmi_msghandler processor button nfsd auth_rpcgss oid_registry nfs_acl lockd grace sunrpc ip_tables x_tables ext4 crc16 mbcache jbd2 sd_mod hid_generic usbhid hid ahci libahci libata igb ehci_pci hwmon ehci_hcd ptp usbcore pps_core scsi_mod i2c_algo_bit usb_common i2c_core dca autofs4 [last unloaded: mlx4_core]
kernel: CPU: 2 PID: 6012 Comm: modprobe Tainted: G O L
4.3.0-rc3-debug+ #67
kernel: Hardware name: Supermicro SYS-1027R-WRF/X9DRW, BIOS 3.0a 08/08/2013
kernel: 000000000000011b ffff8807a99afbe8 ffffffff8129915b 0000000000000009
kernel: 0000000000000000 ffff8807a99afc28 ffffffff810752b5 ffff880827d7c2a0
kernel: ffff8807b0d03260 ffff880827d7c2a0 ffff880827d7cc60 0000000000000000
kernel: Call Trace:
kernel:  [<ffffffff8129915b>] dump_stack+0x4f/0x74
kernel:  [<ffffffff810752b5>] warn_slowpath_common+0x95/0xe0
kernel:  [<ffffffff8107531a>] warn_slowpath_null+0x1a/0x20
kernel:  [<ffffffffa001bd4b>] ib_dealloc_pd+0x5b/0xa0 [ib_core]
kernel:  [<ffffffffa047adce>] ipoib_transport_dev_cleanup+0x9e/0xf0
[ib_ipoib]
kernel:  [<ffffffffa047712e>] ipoib_ib_dev_cleanup+0x5e/0x80 [ib_ipoib]
kernel:  [<ffffffffa0473984>] ipoib_dev_cleanup+0x2a4/0x3b0 [ib_ipoib]
kernel:  [<ffffffff8107a11d>] ? __local_bh_enable_ip+0x6d/0xd0
kernel:  [<ffffffffa0473a9e>] ipoib_uninit+0xe/0x10 [ib_ipoib]
kernel:  [<ffffffff8141ba17>] rollback_registered_many+0x1a7/0x2c0
kernel:  [<ffffffff8141bbd1>] rollback_registered+0x31/0x40
kernel:  [<ffffffff8141bc38>] unregister_netdevice_queue+0x58/0xb0
kernel:  [<ffffffff8141be00>] unregister_netdev+0x20/0x30
kernel:  [<ffffffffa04721a1>] ipoib_remove_one+0xa1/0xe0 [ib_ipoib]
kernel:  [<ffffffffa001e0d1>] ib_unregister_device+0xc1/0x160 [ib_core]
kernel:  [<ffffffffa05231f9>] mlx5_ib_remove+0x19/0x50 [mlx5_ib]
kernel:  [<ffffffffa04e5068>] mlx5_remove_device+0x68/0x80 [mlx5_core]
kernel:  [<ffffffffa04e50be>] mlx5_unregister_interface+0x3e/0x70
[mlx5_core]
kernel:  [<ffffffffa053397c>] mlx5_ib_cleanup+0x10/0x694 [mlx5_ib]
kernel:  [<ffffffff810f67aa>] SyS_delete_module+0x17a/0x1c0
kernel:  [<ffffffff81003017>] ? trace_hardirqs_on_thunk+0x17/0x19
kernel:  [<ffffffff811e80b0>] ? generic_show_options+0x180/0x180
kernel:  [<ffffffff8151a1f2>] entry_SYSCALL_64_fastpath+0x12/0x76
kernel: ---[ end trace 31339c7283574ccb ]---

Quoted 4 lines

--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html

--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html

Or Gerlitz

2015-10-07 19:12 UTC #11 lore raw

In reply to a message not in the archive

Quoted 3 lines · Sagi Grimberg

This started popping up (not sure if it's new to 4.3-rc1). Happens when unloading the provider driver (mlx4/mlx5 in my case). Has anyone seen this?

yes, I think to see it over the last 1-2 years

Or.
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html