The general protection fault is reproducible with the current 5.3 kernel as follows by creating 10 SR-IOV enabled VMs with OpenStack and deleting 5 VMs sequentially. After updating it to the -proposed one as linux-image-5.3.0-25-generic 5.3.0-25.27, there is no such general protection fault happened with the same operations. So we can consider the fix is verified.
=== Dec 08 08:39:07 hostname kernel: i40e 0000:af:00.1: Bring down and up the VF interface to make this change effective. Dec 08 08:39:07 hostname kernel: general protection fault: 0000 [#1] SMP PTI Dec 08 08:39:07 hostname kernel: CPU: 36 PID: 3225 Comm: libvirtd Not tainted 5.3.0-24-generic #26~18.04.2-Ubuntu Dec 08 08:39:07 hostname kernel: Hardware name: HPE ProLiant DL380 Gen10/ProLiant DL380 Gen10, BIOS U30 05/21/2019 Dec 08 08:39:07 hostname kernel: RIP: 0010:i40e_config_vf_promiscuous_mode+0x172/0x330 [i40e] Dec 08 08:39:07 hostname kernel: Code: 48 8b 00 83 d1 00 48 85 c0 75 ef 49 83 c4 08 4c 39 e6 75 dd 85 c9 74 73 0f b6 45 c0 45 31 d2 89 45 d0 4d 8b 3e 4d 85 ff 74 53 <41> 0f b7 4f 16 Dec 08 08:39:07 hostname kernel: RSP: 0018:ffffa7045d32b760 EFLAGS: 00010202 Dec 08 08:39:07 hostname kernel: RAX: 0000000000000000 RBX: ffff94e379bdb000 RCX: 0000000000000000 Dec 08 08:39:07 hostname kernel: RDX: 0000000000000000 RSI: 0000000006000000 RDI: ffff9583a4424350 Dec 08 08:39:07 hostname kernel: RBP: ffffa7045d32b7b0 R08: 0000000000000000 R09: ffff9583a54d95e0 Dec 08 08:39:07 hostname kernel: R10: 0000000000000000 R11: 0000000000000100 R12: ffff94e379bdba28 Dec 08 08:39:07 hostname kernel: R13: ffff9583a4424008 R14: ffff94e379bdb338 R15: 010eb7eb8c61c8cb Dec 08 08:39:07 hostname kernel: FS: 00007f495b017700(0000) GS:ffff9533bfa80000(0000) knlGS:0000000000000000 Dec 08 08:39:07 hostname kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Dec 08 08:39:07 hostname kernel: CR2: 00007f4967d89360 CR3: 0000004d839c0004 CR4: 00000000007626e0 Dec 08 08:39:07 hostname kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 Dec 08 08:39:07 hostname kernel: DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Dec 08 08:39:07 hostname kernel: PKRU: 55555554 Dec 08 08:39:07 hostname kernel: Call Trace: Dec 08 08:39:07 hostname kernel: i40e_ndo_set_vf_port_vlan+0x1a2/0x440 [i40e] Dec 08 08:39:07 hostname kernel: do_setlink+0x53f/0xee0 Dec 08 08:39:07 hostname kernel: ? update_load_avg+0x596/0x620 Dec 08 08:39:07 hostname kernel: ? update_curr+0x7a/0x1d0 Dec 08 08:39:07 hostname kernel: ? __switch_to_asm+0x40/0x70 Dec 08 08:39:07 hostname kernel: ? __switch_to_asm+0x34/0x70 ** Tags removed: verification-needed-eoan ** Tags added: verification-done-eoan -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1852663 Title: i40e: general protection fault in i40e_config_vf_promiscuous_mode Status in linux package in Ubuntu: In Progress Status in linux source package in Eoan: Fix Committed Bug description: SRU Justification [Impact] Assign some VFs to VMs, when deleting VMs, a general protection fault occurs in i40e_config_vf_promiscuous_mode general protection fault: 0000 [#1] SMP PTI CPU: 54 PID: 6200 Comm: libvirtd Not tainted 5.3.0-21-generic #22~18.04.1-UbuntuHardware name: HPE ProLiant DL380 Gen10/ProLiant DL380 Gen10, BIOS U30 05/21/2019 RIP: 0010:i40e_config_vf_promiscuous_mode+0x172/0x330 [i40e] Code: 48 8b 00 83 d1 00 48 85 c0 75 ef 49 83 c4 08 4c 39 e6 75 dd 85 c9 74 73 0f b6 45 c0 45 31 d2 89 45 d0 4d 8b 3e 4d 85 ff 74 53 <41> 0f b7 4f 16 66 81 f9 ff 0f 77 3f 0f b7 b3 ea 0c 00 00 8b 55 d0 RSP: 0018:ffffb987b5c77760 EFLAGS: 00010202 RAX: 0000000000000000 RBX: ffff9bb5df5a9000 RCX: 0000000000000000 RDX: 0000000000000000 RSI: 0000000006000000 RDI: ffff9bace4bce350 RBP: ffffb987b5c777b0 R08: 0000000000000000 R09: ffff9bace56a9da0 R10: 0000000000000000 R11: 0000000000000100 R12: ffff9bb5df5a9a28 R13: ffff9bace4bce008 R14: ffff9bb5df5a9338 R15: 26c2b975d54f5980 FS: 00007f9f07fff700(0000) GS:ffff9bfcff480000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007fa73c9c0e10 CR3: 000000f6ab37a002 CR4: 00000000007626e0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 PKRU: 55555554 Call Trace: i40e_ndo_set_vf_port_vlan+0x1a2/0x440[i40e] do_setlink+0x53f/0xee0 ?update_load_avg+0x596/0x620 ?update_curr+0x7a/0x1d0 ?__switch_to_asm+0x40/0x70 ?__switch_to_asm+0x34/0x70 ?__switch_to_asm+0x40/0x70 ?__switch_to_asm+0x34/0x70 rtnl_setlink+0x113/0x150 rtnetlink_rcv_msg+0x296/0x340 ?aa_label_sk_perm.part.4+0x10f/0x160 ?_cond_resched+0x19/0x40 ?rtnl_calcit.isra.30+0x120/0x120 netlink_rcv_skb+0x51/0x120 rtnetlink_rcv+0x15/0x20 netlink_unicast+0x1a4/0x250 netlink_sendmsg+0x2d7/0x3d0 sock_sendmsg+0x63/0x70 ___sys_sendmsg+0x2a9/0x320 ?aa_label_sk_perm.part.4+0x10f/0x160 ?_raw_spin_unlock_bh+0x1e/0x20 ?release_sock+0x8f/0xa0 __sys_sendmsg+0x63/0xa0 ?__sys_sendmsg+0x63/0xa0 __x64_sys_sendmsg+0x1f/0x30 do_syscall_64+0x5a/0x130 entry_SYSCALL_64_after_hwframe+0x44/0xa9 This issue also happens when deleting k8s pod if VF is used by k8s pod, there was a bug reported in the e1000-devel mailing list https://sourceforge.net/p/e1000/mailman/message/36766306/ The fix is suggested by Billy McFall, to add protection when accessing the hash list(vsi->mac_filter_hash), but it's not upstream yet [Test Case] Spin up some VMs with VFs, then delete all VMs [Regression Potential] Low, the fix is to add a protection for a hash list, shouldn't have potential regression To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1852663/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
