[Kernel-packages] [Bug 2021571] Re: cat /sys/fs/cgroup/blkio/blkio.time_recursive took 1second to complete
do you know what __percpu_counter_sum does? I am wondering why it has been sampled a lot of times. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/2021571 Title: cat /sys/fs/cgroup/blkio/blkio.time_recursive took 1second to complete Status in linux-meta package in Ubuntu: Confirmed Bug description: Issue: ```console # time cat /sys/fs/cgroup/blkio/blkio.time_recursive 8:16 354721435 real0m1.297s user0m0.000s sys 0m1.297s ``` As could be seen from above result, cat blkio took about 1 second to complete which is much longer than a normal case. Kernel Version: Linux compute08 4.15.0-72-generic #81-Ubuntu SMP Tue Nov 26 12:20:02 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux Would be appreciated to know any operations to identify the issue, Thank you very much for the help. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/2021571/+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
[Kernel-packages] [Bug 2021571] Re: cat /sys/fs/cgroup/blkio/blkio.time_recursive took 1second to complete
I have no idea what racadm is .. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/2021571 Title: cat /sys/fs/cgroup/blkio/blkio.time_recursive took 1second to complete Status in linux-meta package in Ubuntu: Confirmed Bug description: Issue: ```console # time cat /sys/fs/cgroup/blkio/blkio.time_recursive 8:16 354721435 real0m1.297s user0m0.000s sys 0m1.297s ``` As could be seen from above result, cat blkio took about 1 second to complete which is much longer than a normal case. Kernel Version: Linux compute08 4.15.0-72-generic #81-Ubuntu SMP Tue Nov 26 12:20:02 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux Would be appreciated to know any operations to identify the issue, Thank you very much for the help. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/2021571/+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
[Kernel-packages] [Bug 2021571] Re: cat /sys/fs/cgroup/blkio/blkio.time_recursive took 1second to complete
we might have around 50 multipath mappers per node and underline device is FC based disk. But disks added/removed should not be frequent. What machine are you using? For me, some nodes are intel 2650, not sure if it is relevant. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/2021571 Title: cat /sys/fs/cgroup/blkio/blkio.time_recursive took 1second to complete Status in linux-meta package in Ubuntu: Confirmed Bug description: Issue: ```console # time cat /sys/fs/cgroup/blkio/blkio.time_recursive 8:16 354721435 real0m1.297s user0m0.000s sys 0m1.297s ``` As could be seen from above result, cat blkio took about 1 second to complete which is much longer than a normal case. Kernel Version: Linux compute08 4.15.0-72-generic #81-Ubuntu SMP Tue Nov 26 12:20:02 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux Would be appreciated to know any operations to identify the issue, Thank you very much for the help. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/2021571/+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
[Kernel-packages] [Bug 2021571] Re: cat /sys/fs/cgroup/blkio/blkio.time_recursive took 1second to complete
thank you and same for me. __percpu_counter_sum is very slow even though only one block device.. Not really figure why. Do you have any clue to reproduce this behavior? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/2021571 Title: cat /sys/fs/cgroup/blkio/blkio.time_recursive took 1second to complete Status in linux-meta package in Ubuntu: Confirmed Bug description: Issue: ```console # time cat /sys/fs/cgroup/blkio/blkio.time_recursive 8:16 354721435 real0m1.297s user0m0.000s sys 0m1.297s ``` As could be seen from above result, cat blkio took about 1 second to complete which is much longer than a normal case. Kernel Version: Linux compute08 4.15.0-72-generic #81-Ubuntu SMP Tue Nov 26 12:20:02 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux Would be appreciated to know any operations to identify the issue, Thank you very much for the help. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/2021571/+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
[Kernel-packages] [Bug 2021571] Re: cat /sys/fs/cgroup/blkio/blkio.time_recursive took 1second to complete
Hi Kevin, have you used perf and analyze the flamegraph? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/2021571 Title: cat /sys/fs/cgroup/blkio/blkio.time_recursive took 1second to complete Status in linux-meta package in Ubuntu: Confirmed Bug description: Issue: ```console # time cat /sys/fs/cgroup/blkio/blkio.time_recursive 8:16 354721435 real0m1.297s user0m0.000s sys 0m1.297s ``` As could be seen from above result, cat blkio took about 1 second to complete which is much longer than a normal case. Kernel Version: Linux compute08 4.15.0-72-generic #81-Ubuntu SMP Tue Nov 26 12:20:02 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux Would be appreciated to know any operations to identify the issue, Thank you very much for the help. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/2021571/+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
[Kernel-packages] [Bug 2021571] [NEW] cat /sys/fs/cgroup/blkio/blkio.time_recursive took 1second to complete
Public bug reported: Issue: ```console # time cat /sys/fs/cgroup/blkio/blkio.time_recursive 8:16 354721435 real0m1.297s user0m0.000s sys 0m1.297s ``` As could be seen from above result, cat blkio took about 1 second to complete which is much longer than a normal case. Kernel Version: Linux compute08 4.15.0-72-generic #81-Ubuntu SMP Tue Nov 26 12:20:02 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux Would be appreciated to know any operations to identify the issue, Thank you very much for the help. ** Affects: linux-meta (Ubuntu) Importance: Undecided Status: New ** Description changed: Issue: ```console - # time cat /sys/fs/cgroup/blkio/blkio.time_recursive + # time cat /sys/fs/cgroup/blkio/blkio.time_recursive 8:16 354721435 real0m1.297s user0m0.000s sys 0m1.297s ``` As could be seen from above result, cat blkio took about 1 second to complete which is much longer than a normal case. Kernel Version: Linux compute08 4.15.0-72-generic #81-Ubuntu SMP Tue Nov 26 12:20:02 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux + + + Would be appreciated to know any operations to identify the issue, Thank you very much for the help. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/2021571 Title: cat /sys/fs/cgroup/blkio/blkio.time_recursive took 1second to complete Status in linux-meta package in Ubuntu: New Bug description: Issue: ```console # time cat /sys/fs/cgroup/blkio/blkio.time_recursive 8:16 354721435 real0m1.297s user0m0.000s sys 0m1.297s ``` As could be seen from above result, cat blkio took about 1 second to complete which is much longer than a normal case. Kernel Version: Linux compute08 4.15.0-72-generic #81-Ubuntu SMP Tue Nov 26 12:20:02 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux Would be appreciated to know any operations to identify the issue, Thank you very much for the help. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/2021571/+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
[Kernel-packages] [Bug 1837810] Re: KVM: Fix zero_page reference counter overflow when using KSM on KVM compute host
Thank you very much for the reply. Another question is try_get_page returns -ENOMEM but kvm warning is bad address which should be EFAULT. Why qemu prints error log says bad address? -- 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/1837810 Title: KVM: Fix zero_page reference counter overflow when using KSM on KVM compute host Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Status in linux source package in Focal: Fix Released Bug description: BugLink: https://bugs.launchpad.net/bugs/1837810 [Impact] We are seeing a problem on OpenStack compute nodes, and KVM hosts, where a kernel oops is generated, and all running KVM machines are placed into the pause state. This is caused by the kernel's reserved zero_page reference counter overflowing from a positive number to a negative number, and hitting a (WARN_ON_ONCE(page_ref_count(page) <= 0)) condition in try_get_page(). This only happens if the machine has Kernel Samepage Mapping (KSM) enabled, with "use_zero_pages" turned on. Each time a new VM starts and the kernel does a KSM merge run during a EPT violation, the reference counter for the zero_page is incremented in try_async_pf() and never decremented. Eventually, the reference counter will overflow, causing the KVM subsystem to fail. Syslog: error : qemuMonitorJSONCheckError:392 : internal error: unable to execute QEMU command 'cont': Resetting the Virtual Machine is required QEMU Logs: error: kvm run failed Bad address EAX=000afe00 EBX=000b ECX=0080 EDX=0cfe ESI=0003fe00 EDI=000afe00 EBP=0007 ESP=6d74 EIP=000ee344 EFL=00010002 [---] CPL=0 II=0 A20=1 SMM=0 HLT=0 ES =0010 00c09300 DPL=0 DS [-WA] CS =0008 00c09b00 DPL=0 CS32 [-RA] SS =0010 00c09300 DPL=0 DS [-WA] DS =0010 00c09300 DPL=0 DS [-WA] FS =0010 00c09300 DPL=0 DS [-WA] GS =0010 00c09300 DPL=0 DS [-WA] LDT= 8200 DPL=0 LDT TR = 8b00 DPL=0 TSS32-busy GDT= 000f7040 0037 IDT= 000f707e CR0=0011 CR2= CR3= CR4= DR0= DR1= DR2= DR3= DR6=0ff0 DR7=0400 EFER= Code=c3 57 56 b8 00 fe 0a 00 be 00 fe 03 00 b9 80 00 00 00 89 c7 a5 a1 00 80 03 00 8b 15 04 80 03 00 a3 00 80 0a 00 89 15 04 80 0a 00 b8 ae e2 00 00 31 Kernel Oops: [ 167.695986] WARNING: CPU: 1 PID: 3016 at /build/linux-hwe-FEhT7y/linux-hwe-4.15.0/include/linux/mm.h:852 follow_page_pte+0x6f4/0x710 [ 167.696023] CPU: 1 PID: 3016 Comm: CPU 0/KVM Tainted: G OE 4.15.0-106-generic #107~16.04.1-Ubuntu [ 167.696023] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.13.0-1ubuntu1 04/01/2014 [ 167.696025] RIP: 0010:follow_page_pte+0x6f4/0x710 [ 167.696026] RSP: 0018:a81802023908 EFLAGS: 00010286 [ 167.696027] RAX: ed8786e33a80 RBX: ed878c6d21b0 RCX: 8000 [ 167.696027] RDX: RSI: 3000 RDI: 8001b8cea225 [ 167.696028] RBP: a81802023970 R08: 8001b8cea225 R09: 90c4d55fa340 [ 167.696028] R10: R11: R12: ed8786e33a80 [ 167.696029] R13: 0326 R14: 90c4db94fc50 R15: 90c4d55fa340 [ 167.696030] FS: 7f6a7798c700() GS:90c4edc8() knlGS: [ 167.696030] CS: 0010 DS: ES: CR0: 80050033 [ 167.696031] CR2: CR3: 000315580002 CR4: 00162ee0 [ 167.696033] Call Trace: [ 167.696047] follow_pmd_mask+0x273/0x630 [ 167.696049] follow_page_mask+0x178/0x230 [ 167.696051] __get_user_pages+0xb8/0x740 [ 167.696052] get_user_pages+0x42/0x50 [ 167.696068] __gfn_to_pfn_memslot+0x18b/0x3b0 [kvm] [ 167.696079] ? mmu_set_spte+0x1dd/0x3a0 [kvm] [ 167.696090] try_async_pf+0x66/0x220 [kvm] [ 167.696101] tdp_page_fault+0x14b/0x2b0 [kvm] [ 167.696104] ? vmexit_fill_RSB+0x10/0x40 [kvm_intel] [ 167.696114] kvm_mmu_page_fault+0x62/0x180 [kvm] [ 167.696117] handle_ept_violation+0xbc/0x160 [kvm_intel] [ 167.696119] vmx_handle_exit+0xa5/0x580 [kvm_intel] [ 167.696129] vcpu_enter_guest+0x414/0x1260 [kvm] [ 167.696138] ? kvm_arch_vcpu_load+0x4d/0x280 [kvm] [ 167.696148] kvm_arch_vcpu_ioctl_run+0xd9/0x3d0 [kvm] [ 167.696157] ? kvm_arch_vcpu_ioctl_run+0xd9/0x3d0 [kvm] [ 167.696165] kvm_vcpu_ioctl+0x33a/0x610 [kvm] [ 167.696166] ? do_futex+0x129/0x590 [ 167.696171] ? __switch_to+0x34c/0x4e0 [ 167.696174] ? __switch_to_asm+0x35/0x70 [ 167.696176] do_vfs_ioctl+0xa4/0x600 [ 167.696177] SyS_ioctl+0x79/0x90 [
[Kernel-packages] [Bug 1763062] Re: LSM stacking patches for bionic
https://answers.launchpad.net/ubuntu/+question/698319 -- 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/1763062 Title: LSM stacking patches for bionic Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Bug description: LSM stacking patches for bionic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1763062/+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
[Kernel-packages] [Bug 1713997] Re: kexec-tools should not ask to handle reboots
may I ask why reboots via kexec-tools only supported on sysv init systemd? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to kexec-tools in Ubuntu. https://bugs.launchpad.net/bugs/1713997 Title: kexec-tools should not ask to handle reboots Status in kexec-tools package in Ubuntu: Confirmed Bug description: Reboots via kexec-tools are only supported on SysV init systems. With systemd the only supported init system by now, kexec-tools should no longer ask (during installation) if reboots should be handled by kexec-tools. There should be no user interaction required when installing the package. $ lsb_release -rd Description: Ubuntu Artful Aardvark (development branch) Release: 17.10 $ apt-cache policy kexec-tools kexec-tools: Installed: 1:2.0.15-0ubuntu1 Candidate: 1:2.0.15-0ubuntu1 Version table: *** 1:2.0.15-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu artful/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kexec-tools/+bug/1713997/+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
[Kernel-packages] [Bug 1908090] Re: ubuntu 20.04 kdump fails
hello, may I ask how did you capture the log? My kdump also stuck but unfortunately does not print anything. the system looks dead though. the vm got a memory size of 4GiB -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to kexec-tools in Ubuntu. https://bugs.launchpad.net/bugs/1908090 Title: ubuntu 20.04 kdump fails Status in kexec-tools package in Ubuntu: New Bug description: When linux-crashdump (5.4.0.58.61) is enabled on Ubuntu 20.04 LTS, everything appears to be in good working order, according to "systemctl status kdump-tools" and "kdump-config status". However, upon an actual crash, the system hangs, and no crash files are produced. I've investigated and have learned that the capture kernel does indeed start, but it is unable to unpack the rootfs/initrd, and thus fails and hangs. [1.070469] Trying to unpack rootfs image as initramfs... [1.333182] swapper/0 invoked oom-killer: gfp_mask=0x100cc2(GFP_HIGHUSER), order=0, oom_score_adj=0 [1.335074] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 5.4.0-26-generic #30-Ubuntu [1.336396] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Ubuntu-1.8.2-1ubuntu1 04/01/2014 [1.336396] Call Trace: [1.336396] dump_stack+0x6d/0x9a [1.336396] dump_header+0x4f/0x1eb [1.336396] out_of_memory.part.0.cold+0x39/0x83 [1.336396] out_of_memory+0x6d/0xd0 ... [1.413202] ---[ end Kernel panic - not syncing: System is deadlocked on memory ]--- On this system with 8G of memory, the crash memory as specified on the kernel command line is "crashkernel=512M-:192M". I changed the 192M to 256M, and now kdump works. Not sure how the 192M value is chosen, but it does not work. I think this used value used to work for 16.04 and maybe 18.04 (I didn't try), but is no longer useful for 20.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kexec-tools/+bug/1908090/+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
[Kernel-packages] [Bug 1837810] Re: KVM: Fix zero_page reference counter overflow when using KSM on KVM compute host
Interestingly, I hit this warning log without enabling ksm ```console # cat /sys/kernel/mm/ksm/run 0 # uname -a Linux compute12 4.15.0-72-generic #81-Ubuntu SMP Tue Nov 26 12:20:02 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux # lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 18.04.3 LTS Release:18.04 Codename: bionic ``` log is [Sat May 15 11:28:32 2021] WARNING: CPU: 31 PID: 3196546 at /build/linux-E6MDAa/linux-4.15.0/include/linux/mm.h:857 follow_page_pte+0x663/0x6d0 [Sat May 15 11:28:32 2021] Modules linked in: nls_iso8859_1 act_police cls_u32 sch_ingress cls_fw sch_sfq sch_htb ip6table_raw xt_CT xt_mac vhost_net vhost tap ebtable_filter ebtables ip6table_filter devlink vxlan ip6_udp_tunnel udp_tunnel ip_gre gre xt_multiport xt_set iptable_raw iptable_mangle ip_set_hash_net ip_set_hash_ip ip_set ipip tunnel4 ip_tunnel veth xt_statistic xt_physdev xt_nat xt_recent ipt_REJECT nf_reject_ipv4 xt_tcpudp xt_addrtype ip_vs_sh ip_vs_wrr ip_vs_rr ip_vs ip6table_nat ip6_tables xt_comment xt_mark iptable_filter xt_conntrack nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat aufs rbd libceph overlay openvswitch nsh nf_conntrack_ipv6 nf_nat_ipv6 nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_defrag_ipv6 nf_nat bonding dm_service_time dm_multipath [Sat May 15 11:28:32 2021] scsi_dh_rdac scsi_dh_emc scsi_dh_alua intel_rapl skx_edac x86_pkg_temp_thermal coretemp kvm_intel kvm irqbypass intel_cstate intel_rapl_perf ipmi_ssif ioatdma joydev input_leds acpi_power_meter mei_me mei shpchp mac_hid ipmi_si ipmi_devintf ipmi_msghandler lpc_ich sch_fq_codel nf_conntrack ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi br_netfilter bridge stp llc ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear ses enclosure scsi_transport_sas hid_generic crct10dif_pclmul crc32_pclmul usbhid ghash_clmulni_intel hid pcbc lpfc aesni_intel aes_x86_64 nvmet_fc crypto_simd ast glue_helper nvmet cryptd nvme_fc ttm nvme_fabrics [Sat May 15 11:28:32 2021] igb nvme_core drm_kms_helper dca scsi_transport_fc syscopyarea i2c_algo_bit sysfillrect sysimgblt i40e aacraid fb_sys_fops drm ptp pps_core ahci libahci wmi [Sat May 15 11:28:32 2021] CPU: 31 PID: 3196546 Comm: CPU 2/KVM Not tainted 4.15.0-72-generic #81-Ubuntu [Sat May 15 11:28:32 2021] Hardware name: Inspur NF5280M5/YZMB-00882-104, BIOS 4.0.8 10/17/2018 [Sat May 15 11:28:32 2021] RIP: 0010:follow_page_pte+0x663/0x6d0 [Sat May 15 11:28:32 2021] RSP: 0018:b1eff4e5b8f8 EFLAGS: 00010286 [Sat May 15 11:28:32 2021] RAX: e041b58cba40 RBX: e043fed90cf0 RCX: 8000 [Sat May 15 11:28:32 2021] RDX: e041b58cba40 RSI: 7f7306766000 RDI: 800d632e9225 [Sat May 15 11:28:32 2021] RBP: b1eff4e5b960 R08: 800d632e9225 R09: a0249cceb1e0 [Sat May 15 11:28:32 2021] R10: R11: b1eff4e5ba8c R12: e041b58cba40 [Sat May 15 11:28:32 2021] R13: 3000 R14: 0326 R15: a076af75a198 [Sat May 15 11:28:32 2021] FS: 7f73f48ee700() GS:a0947f2c() knlGS:f88001e81000 [Sat May 15 11:28:32 2021] CS: 0010 DS: ES: CR0: 80050033 [Sat May 15 11:28:32 2021] CR2: f8a016819000 CR3: 004e72518004 CR4: 007626e0 [Sat May 15 11:28:32 2021] DR0: DR1: DR2: [Sat May 15 11:28:32 2021] DR3: DR6: fffe0ff0 DR7: 0400 [Sat May 15 11:28:32 2021] PKRU: 5554 [Sat May 15 11:28:32 2021] Call Trace: [Sat May 15 11:28:32 2021] follow_pmd_mask+0x209/0x640 [Sat May 15 11:28:32 2021] follow_page_mask+0x17a/0x210 [Sat May 15 11:28:32 2021] __get_user_pages+0x18c/0x720 [Sat May 15 11:28:32 2021] get_user_pages+0x42/0x50 [Sat May 15 11:28:32 2021] __gfn_to_pfn_memslot+0x126/0x410 [kvm] [Sat May 15 11:28:32 2021] try_async_pf+0x66/0x1f0 [kvm] [Sat May 15 11:28:32 2021] tdp_page_fault+0x138/0x290 [kvm] [Sat May 15 11:28:32 2021] ? vmexit_fill_RSB+0x1c/0x40 [kvm_intel] [Sat May 15 11:28:32 2021] kvm_mmu_page_fault+0x62/0x160 [kvm] [Sat May 15 11:28:32 2021] handle_ept_violation+0xbb/0x150 [kvm_intel] [Sat May 15 11:28:32 2021] vmx_handle_exit+0xb3/0xe80 [kvm_intel] [Sat May 15 11:28:32 2021] ? vmexit_fill_RSB+0x1c/0x40 [kvm_intel] [Sat May 15 11:28:32 2021] ? vmexit_fill_RSB+0x10/0x40 [kvm_intel] [Sat May 15 11:28:32 2021] ? vmexit_fill_RSB+0x1c/0x40 [kvm_intel] [Sat May 15 11:28:32 2021] ? vmexit_fill_RSB+0x10/0x40 [kvm_intel] [Sat May 15 11:28:32 2021] ? vmx_vcpu_run+0x3fa/0x600 [kvm_intel] [Sat May 15 11:28:32 2021] vcpu_enter_guest+0x424/0x1260 [kvm] [Sat May 15 11:28:32 2021] ? __schedule+0x256/0x880 [Sat May 15 11:28:32 2021] kvm_arch_vcpu_ioctl_run+0x203/0x3e0 [kvm] [Sat May 15 11:28:32 2021] ? kvm_arch_vcpu
[Kernel-packages] [Bug 1786752] Re: Reference counter issue in 4.15 (nf_xfrm_me_harder / dst_release)
Hi, sorry to ask non related questions. But could youe please teach how did you identity there is a negative refcnts from the dmesg? thanks... -- 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/1786752 Title: Reference counter issue in 4.15 (nf_xfrm_me_harder / dst_release) Status in linux package in Ubuntu: Confirmed Bug description: Since upgrading from 14.04 to 18.04, we see very frequent warnings about negative refcnts in dst_release: [ 3117.882227] WARNING: CPU: 6 PID: 0 at /build/linux-I4R9hO/linux-4.15.0/include/net/dst.h:256 nf_xfrm_me_harder+0x127/0x140 [nf_nat] [ 3117.882229] Modules linked in: xt_policy cls_u32 sch_sfq ip_vti ip_tunnel authenc echainiv xfrm6_mode_tunnel xfrm4_mode_tunnel xfrm4_tunnel tunnel4 ipcomp xfrm_ipcomp esp4 ah4 af_key nfnetlink_queue nfnetlink_log sch_htb xt_TPROXY xt_multiport veth nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo br_netfilter bridge overlay macvlan 8021q garp mrp stp llc bonding algif_skcipher af_alg xt_hl ip6t_rt nf_conntrack_ipv6 nf_defrag_ipv6 ip6t_REJECT nf_reject_ipv6 xt_nat ipt_MASQUERADE nf_nat_masquerade_ipv4 dm_crypt iptable_nat nf_nat_ipv4 xt_DSCP xt_dscp xt_mark iptable_mangle xt_limit xt_tcpudp xt_addrtype intel_rapl sb_edac x86_pkg_temp_thermal intel_powerclamp coretemp nf_conntrack_ipv4 nf_defrag_ipv4 kvm_intel xt_conntrack kvm joydev input_leds ipt_REJECT nf_reject_ipv4 ftdi_sio usbserial ipmi_si [ 3117.882265] irqbypass intel_cstate mei_me mei ioatdma acpi_pad intel_rapl_perf shpchp ipmi_devintf ipmi_msghandler acpi_power_meter lpc_ich mac_hid ip6table_filter ip6_tables nf_conntrack_netbios_ns nf_conntrack_broadcast nf_nat_ftp nf_nat nf_conntrack_ftp sch_fq_codel nf_conntrack iptable_filter ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear mgag200 ttm crct10dif_pclmul igb ixgbe crc32_pclmul drm_kms_helper hid_generic ghash_clmulni_intel syscopyarea i2c_algo_bit dca sysfillrect usbhid pcbc sysimgblt fb_sys_fops aesni_intel aes_x86_64 crypto_simd ahci glue_helper ptp hid mxm_wmi cryptd [ 3117.882309] drm libahci megaraid_sas pps_core mdio wmi [ 3117.882315] CPU: 6 PID: 0 Comm: swapper/6 Tainted: GW 4.15.0-30-generic #32-Ubuntu [ 3117.882316] Hardware name: Intel Corporation S2600WT2R/S2600WT2R, BIOS SE5C610.86B.01.01.0022.062820171903 06/28/2017 [ 3117.882319] RIP: 0010:nf_xfrm_me_harder+0x127/0x140 [nf_nat] [ 3117.882320] RSP: 0018:88d77f3839f0 EFLAGS: 00010246 [ 3117.882322] RAX: RBX: 90de4000 RCX: 1924 [ 3117.882323] RDX: RSI: 88d749ae6400 RDI: 88d655e96600 [ 3117.882324] RBP: 88d77f383a68 R08: 88d7493dc000 R09: 0018 [ 3117.882324] R10: 0001 R11: 88e770dedc00 R12: 88d655e96600 [ 3117.882325] R13: 88d77f383ae8 R14: 88d7799ff200 R15: 88d7493dc000 [ 3117.882327] FS: () GS:88d77f38() knlGS: [ 3117.882327] CS: 0010 DS: ES: CR0: 80050033 [ 3117.882328] CR2: ff600400 CR3: 00193de0a002 CR4: 003606e0 [ 3117.882329] DR0: DR1: DR2: [ 3117.882330] DR3: DR6: fffe0ff0 DR7: 0400 [ 3117.882331] Call Trace: [ 3117.882332] [ 3117.882337] ? nf_nat_ipv4_fn+0x15b/0x200 [nf_nat_ipv4] [ 3117.882339] nf_nat_ipv4_out+0xc5/0xe0 [nf_nat_ipv4] [ 3117.882342] iptable_nat_ipv4_out+0x15/0x20 [iptable_nat] [ 3117.882347] nf_hook_slow+0x48/0xc0 [ 3117.882353] ip_output+0xd2/0xe0 [ 3117.882355] ? ip_fragment.constprop.44+0x80/0x80 [ 3117.882357] ip_forward_finish+0x49/0x70 [ 3117.882359] ip_forward+0x366/0x440 [ 3117.882361] ? ip_frag_mem+0x20/0x20 [ 3117.882362] ip_rcv_finish+0x129/0x430 [ 3117.882364] ip_rcv+0x28f/0x3a0 [ 3117.882366] ? inet_del_offload+0x40/0x40 [ 3117.882372] __netif_receive_skb_core+0x432/0xb40 [ 3117.882379] ? handle_edge_irq+0x7c/0x190 [ 3117.882384] ? irq_exit+0x67/0xc0 [ 3117.882391] ? do_IRQ+0x82/0xd0 [ 3117.882393] __netif_receive_skb+0x18/0x60 [ 3117.882395] ? __netif_receive_skb+0x18/0x60 [ 3117.882397] netif_receive_skb_internal+0x37/0xd0 [ 3117.882398] napi_gro_receive+0xc5/0xf0 [ 3117.882407] ixgbe_clean_rx_irq+0x446/0xe30 [ixgbe] [ 3117.882411] ixgbe_poll+0x256/0x710 [ixgbe] [ 3117.882413] ? do_IRQ+0x82/0xd0 [ 3117.882415] net_rx_action+0x140/0x3a0 [ 3117.882418] __do_softirq+0xdf/0x2b2 [ 3117.882419] irq_exit+0xb6/0xc0 [ 3117.882421] do_IRQ+0x82/0xd0 [ 3117.882423] common_interrupt+0x84/0x84 [ 3117.882424] [ 3117.882427] RIP: 0010:cpuidle_en