misleading kernel warning skb_warn_bad_offload during checksum calculation
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| | linux (Ubuntu) |
Medium
|
Joseph Salisbury | ||
| | Xenial |
Medium
|
Joseph Salisbury | ||
| | Zesty |
Medium
|
Joseph Salisbury | ||
Bug Description
Even when the packet says checksum calculation is unnecessary the kernel will still check the checksum and display a warning that the checksum is bad.
This has been fixed upstream in Kernel 4.11 by commit id: b2504a5dbef3305
We have reports of Ubuntu 16.04 virtual machines (with ip forward enabled) displaying these warnings:
[10480.074664] ------------[ cut here ]------------
[10480.074667] WARNING: CPU: 1 PID: 0 at /build/
[10480.074669] docker0: caps=(0x0000040
[10480.074670] Modules linked in: veth nfsv3 nfs_acl rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace sunrpc fscache ipt_MASQUERADE nf_nat_
[10480.074695] CPU: 1 PID: 0 Comm: swapper/1 Tainted: P W O 4.8.0-52-generic #55~16.04.1-Ubuntu
[10480.074696] Hardware name: Nutanix AHV, BIOS seabios-
[10480.074697] 0000000000000286 ec176c2ae03bc036 ffff8beef5643870 ffffffffb7a2e7b3
[10480.074699] ffff8beef56438c0 0000000000000000 ffff8beef56438b0 ffffffffb768314b
[10480.074702] 0000098cb84fba80 ffff8bed61f82000 ffff8bee9915c000 0000000000000005
[10480.074704] Call Trace:
[10480.074704] <IRQ> [<ffffffffb7a2e
[10480.074708] [<ffffffffb7683
[10480.074710] [<ffffffffb7683
[10480.074713] [<ffffffffb7a35
[10480.074714] [<ffffffffb7d7c
[10480.074716] [<ffffffffb7d80
[10480.074717] [<ffffffffb7d81
[10480.074719] [<ffffffffb7d81
[10480.074720] [<ffffffffc03cd
[10480.074723] [<ffffffffb7d81
[10480.074725] [<ffffffffb7dc5
[10480.074726] [<ffffffffc0402
[10480.074728] [<ffffffffb7dc6
[10480.074729] [<ffffffffb7db9
[10480.074731] [<ffffffffb7dc6
[10480.074733] [<ffffffffb7dc5
[10480.074736] [<ffffffffb7dc2
[10480.074738] [<ffffffffb7dc2
[10480.074739] [<ffffffffb7dc2
[10480.074741] [<ffffffffb7dc0
[10480.074743] [<ffffffffb7dc1
[10480.074744] [<ffffffffb7dc0
[10480.074746] [<ffffffffb7d7e
[10480.074747] [<ffffffffb780a
[10480.074749] [<ffffffffb7d6f
[10480.074751] [<ffffffffb7d7f
[10480.074753] [<ffffffffb7d7f
[10480.074754] [<ffffffffb7d80
[10480.074756] [<ffffffffc0286
[10480.074758] [<ffffffffb76b5
[10480.074760] [<ffffffffc0287
[10480.074762] [<ffffffffb7d7f
[10480.074764] [<ffffffffb7e9d
[10480.074765] [<ffffffffb7688
[10480.074766] [<ffffffffb7e9d
[10480.074768] [<ffffffffb7e9b
[10480.074768] <EOI> [<ffffffffb7664
[10480.074772] [<ffffffffb7637
[10480.074774] [<ffffffffb7638
[10480.074775] [<ffffffffb76c7
[10480.074776] [<ffffffffb76c7
[10480.074778] [<ffffffffb7651
[10480.074781] ---[ end trace 3a9bd18de5564b05 ]---
We have recompiled your latest 16.04.2 kernel with this patch and confirmed that this warning does not happen. Could you please consider including this fix in your next 16.04 LTS release?
CVE References
| malikons (shiraz-malik) wrote : | #1 |
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
apport-collect 1705447
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the Ubuntu Kernel Team.
| Changed in linux (Ubuntu): | |
| status: | New → Incomplete |
| tags: | added: yakkety |
| Changed in linux (Ubuntu): | |
| importance: | Undecided → Medium |
| Changed in linux (Ubuntu Xenial): | |
| status: | New → Triaged |
| Changed in linux (Ubuntu Zesty): | |
| status: | New → Triaged |
| Changed in linux (Ubuntu): | |
| status: | Incomplete → Triaged |
| Changed in linux (Ubuntu Xenial): | |
| importance: | Undecided → Medium |
| Changed in linux (Ubuntu Zesty): | |
| importance: | Undecided → Medium |
| tags: | added: kernel-da-key xenial zesty |
| Joseph Salisbury (jsalisbury) wrote : | #3 |
I built Xenial and Zesty test kernels with commit b2504a5dbef. The test kernels can be downloaded from:
http://
Can you test these kernels and see if they resolve this bug?
Thanks in advance!
| Changed in linux (Ubuntu Xenial): | |
| assignee: | nobody → Joseph Salisbury (jsalisbury) |
| Changed in linux (Ubuntu Zesty): | |
| assignee: | nobody → Joseph Salisbury (jsalisbury) |
| Changed in linux (Ubuntu): | |
| assignee: | nobody → Joseph Salisbury (jsalisbury) |
| status: | Triaged → In Progress |
| Changed in linux (Ubuntu Xenial): | |
| status: | Triaged → In Progress |
| Changed in linux (Ubuntu Zesty): | |
| status: | Triaged → In Progress |
| malikons (shiraz-malik) wrote : | #4 |
Brilliant! Testing it now.
Cheers,
| malikons (shiraz-malik) wrote : | #5 |
Tested with your test kernel and I can confirm that the problem has been resolved.
Thanks a lot!
| Changed in linux (Ubuntu Zesty): | |
| status: | In Progress → Fix Committed |
| Changed in linux (Ubuntu Xenial): | |
| status: | In Progress → Fix Committed |
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-
If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.
See https:/
| tags: | added: verification-needed-xenial |
| tags: | added: verification-needed-zesty |
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-
If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.
See https:/
Hi @malikons,
Would you be able to verify the fix with the xenial and zesty kernels on -proposed?
Thanks.
| malikons (shiraz-malik) wrote : | #9 |
Hi,
Sorry for the delay in responding. I have tested the kernel few days ago and it is working as expected. I do not see anymore kernel warnings.
Thanks,
Shiraz
| tags: |
added: verification-done-xenial verification-done-zesty removed: verification-needed-xenial verification-needed-zesty |
| Launchpad Janitor (janitor) wrote : | #10 |
This bug was fixed in the package linux - 4.4.0-93.116
---------------
linux (4.4.0-93.116) xenial; urgency=low
* linux: 4.4.0-93.116 -proposed tracker (LP: #1709296)
* Creating conntrack entry failure with kernel 4.4.0-89 (LP: #1709032)
- Revert "Revert "netfilter: synproxy: fix conntrackd interaction""
- netfilter: nf_ct_ext: fix possible panic after nf_ct_extend_
* CVE-2017-1000112
- Revert "udp: consistently apply ufo or fragmentation"
- udp: consistently apply ufo or fragmentation
* CVE-2017-1000111
- Revert "net-packet: fix race in packet_set_ring on PACKET_RESERVE"
- packet: fix tp_reserve race in packet_set_ring
* kernel BUG at [tty_ldisc_reinit] mm/slub.c! (LP: #1709126)
- tty: Simplify tty_set_ldisc() exit handling
- tty: Reset c_line from driver's init_termios
- tty: Handle NULL tty->ldisc
- tty: Move tty_ldisc_kill()
- tty: Use 'disc' for line discipline index name
- tty: Refactor tty_ldisc_reinit() for reuse
- tty: Destroy ldisc instance on hangup
* atheros bt failed after S3 (LP: #1706833)
- SAUCE: Bluetooth: Make request workqueue freezable
* The Precision Touchpad(PTP) button sends incorrect event code (LP: #1708372)
- HID: multitouch: handle external buttons for Precision Touchpads
* Set CONFIG_
- [Config] CONFIG_
* xfs slab objects (memory) leak when xfs shutdown is called (LP: #1706132)
- xfs: fix xfs_log_ticket leak in xfs_end_io() after fs shutdown
* Adt tests of src:linux time out often on armhf lxc containers (LP: #1705495)
- [Packaging] tests -- reduce rebuild test to one flavour
* CVE-2017-7495
- ext4: fix data exposure after a crash
* ubuntu/rsi driver downlink wifi throughput drops to 5-6 Mbps when BT
keyboard is connected (LP: #1706991)
- SAUCE: Redpine: enable power save by default for coex mode
- SAUCE: Redpine: uapsd configuration changes
* [Hyper-V] hv_netvsc: Exclude non-TCP port numbers from vRSS hashing
(LP: #1690174)
- hv_netvsc: Exclude non-TCP port numbers from vRSS hashing
* ath10k doesn't report full RSSI information (LP: #1706531)
- ath10k: add per chain RSSI reporting
* ideapad_laptop don't support v310-14isk (LP: #1705378)
- platform/x86: ideapad-laptop: Add several models to no_hw_rfkill
* [8087:0a2b] Failed to load bluetooth firmware(might affect some other Intel
bt devices) (LP: #1705633)
- Bluetooth: btintel: Create common Intel Version Read function
- Bluetooth: Use switch statement for Intel hardware variants
- Bluetooth: Replace constant hw_variant from Intel Bluetooth firmware
filename
- Bluetooth: hci_intel: Fix firmware file name to use hw_variant
- Bluetooth: btintel: Add MODULE_FIRMWARE entries for iBT 3.5 controllers
* xhci_hcd: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2
comp_code 13 (LP: #1667750)
- xhci: Bad Ethernet performance plugged in ASM1042A host
* OpenPower: Some multipaths temporarily have only a single path
(LP: #1696445)
- scsi: ses: don't get power status of SES device slot on probe
...
| Changed in linux (Ubuntu Xenial): | |
| status: | Fix Committed → Fix Released |
| Launchpad Janitor (janitor) wrote : | #11 |
This bug was fixed in the package linux - 4.10.0-33.37
---------------
linux (4.10.0-33.37) zesty; urgency=low
* linux: 4.10.0-33.37 -proposed tracker (LP: #1709303)
* CVE-2017-1000112
- Revert "udp: consistently apply ufo or fragmentation"
- udp: consistently apply ufo or fragmentation
* CVE-2017-1000111
- Revert "net-packet: fix race in packet_set_ring on PACKET_RESERVE"
- packet: fix tp_reserve race in packet_set_ring
* ThunderX: soft lockup on 4.8+ kernels when running qemu-efi with vhost=on
(LP: #1673564)
- irqchip/gic-v3: Add missing system register definitions
- arm64: KVM: Do not use stack-protector to compile EL2 code
- KVM: arm/arm64: vgic-v3: Use PREbits to infer the number of ICH_APxRn_EL2
registers
- KVM: arm/arm64: vgic-v3: Fix nr_pre_bits bitfield extraction
- arm64: Add a facility to turn an ESR syndrome into a sysreg encoding
- KVM: arm/arm64: vgic-v3: Add accessors for the ICH_APxRn_EL2 registers
- KVM: arm64: Make kvm_condition_
- KVM: arm64: vgic-v3: Add hook to handle guest GICv3 sysreg accesses at EL2
- KVM: arm64: vgic-v3: Add ICV_BPR1_EL1 handler
- KVM: arm64: vgic-v3: Add ICV_IGRPEN1_EL1 handler
- KVM: arm64: vgic-v3: Add ICV_IAR1_EL1 handler
- KVM: arm64: vgic-v3: Add ICV_EOIR1_EL1 handler
- KVM: arm64: vgic-v3: Add ICV_AP1Rn_EL1 handler
- KVM: arm64: vgic-v3: Add ICV_HPPIR1_EL1 handler
- KVM: arm64: vgic-v3: Enable trapping of Group-1 system registers
- KVM: arm64: Enable GICv3 Group-1 sysreg trapping via command-line
- KVM: arm64: vgic-v3: Add ICV_BPR0_EL1 handler
- KVM: arm64: vgic-v3: Add ICV_IGNREN0_EL1 handler
- KVM: arm64: vgic-v3: Add misc Group-0 handlers
- KVM: arm64: vgic-v3: Enable trapping of Group-0 system registers
- KVM: arm64: Enable GICv3 Group-0 sysreg trapping via command-line
- arm64: Add MIDR values for Cavium cn83XX SoCs
- [Config] CONFIG_
- arm64: Add workaround for Cavium Thunder erratum 30115
- KVM: arm64: vgic-v3: Add ICV_DIR_EL1 handler
- KVM: arm64: vgic-v3: Add ICV_RPR_EL1 handler
- KVM: arm64: vgic-v3: Add ICV_CTLR_EL1 handler
- KVM: arm64: vgic-v3: Add ICV_PMR_EL1 handler
- KVM: arm64: Enable GICv3 common sysreg trapping via command-line
- KVM: arm64: vgic-v3: Log which GICv3 system registers are trapped
- arm64: KVM: Make unexpected reads from WO registers inject an undef
- KVM: arm64: Log an error if trapping a read-from-
- KVM: arm64: Log an error if trapping a write-to-read-only GICv3 access
* ibmvscsis: Do not send aborted task response (LP: #1689365)
- target: Fix unknown fabric callback queue-full errors
- ibmvscsis: Do not send aborted task response
- ibmvscsis: Clear left-over abort_cmd pointers
- ibmvscsis: Fix the incorrect req_lim_delta
* hisi_sas performance improvements (LP: #1708734)
- scsi: hisi_sas: define hisi_sas_
- scsi: hisi_sas: optimise the usage of hisi_hba.lock
- scsi: hisi_sas: relocate sata_done_v2_hw()
- scsi: hisi_sas: optimise DMA slot memory
* hisi_sas...
| Changed in linux (Ubuntu Zesty): | |
| status: | Fix Committed → Fix Released |
| manojav (manojav) wrote : | #12 |
I am still seeing this issue with
Linux ___ 4.4.0-93-generic #116-Ubuntu SMP Fri Aug 11 21:17:51 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
[214343.266228] ------------[ cut here ]------------
[214343.266235] WARNING: CPU: 1 PID: 10743 at /build/
[214343.266239] tg3: caps=(0x0000000
[214343.266241] Modules linked in: nf_conntrack_
[214343.266302] scsi_transport_
[214343.266347] CPU: 1 PID: 10743 Comm: transmission-da Tainted: G W I 4.4.0-93-generic #116-Ubuntu
[214343.266349] Hardware name: Hewlett-Packard HP Z600 Workstation/0B54h, BIOS 786G4 v03.13 10/13/2010
[214343.266351] 0000000000000286 4281c02c793d7594 ffff880313a434c8 ffffffff813f9f83
[214343.266355] ffff880313a43510 ffffffff81d6f780 ffff880313a43500 ffffffff810812f2
[214343.266358] ffff88030f710300 ffff8803114c0000 0000000000000002 ffff880310cbd6ac
[214343.266361] Call Trace:
[214343.266363] <IRQ> [<ffffffff813f9
[214343.266373] [<ffffffff81081
[214343.266376] [<ffffffff81081
[214343.266381] [<ffffffff81400
[214343.266385] [<ffffffff81735
[214343.266388] [<ffffffff81739
[214343.266391] [<ffffffff81739
[214343.266394] [<ffffffff81739
[214343.266399] [<ffffffff8175e
[214343.266402] [<ffffffff8173a
[214343.266405] [<ffffffff8173a
[214343.266410] [<ffffffff81743
[214343.266415] [<ffffffff81779
[214343.266420] [<ffff...
| manojav (manojav) wrote : | #13 |
| Joseph Salisbury (jsalisbury) wrote : | #14 |
@manojav, since the original bug reporter, mailkons, says this bug is now fixed, you may want to open a new separate bug to track your issue.
| manojav (manojav) wrote : | #15 |
I am confirm that after I moved to the 4.4.0-95-generic kernel from the proposed repository this, I dont see this issue any longer.
| Changed in linux (Ubuntu): | |
| status: | In Progress → Fix Released |
| Saverio Proto (zioproto) wrote : | #16 |
Hello,
I still se this issue on Xenial with Kernel 4.4.0-93-generic #116-Ubuntu
The server is bare-metal.
It is just a cosmetic problem in the log files or I should upgrade as soon as possible ? I noticed the bad entries in my kern.log with my monitoring tool, but I dont see any side effect so far.
Could anyone please clarify what is the operational impact of this bug ? thanks !
We noticed the same kernel warning with the latest LTS kernel:
[ 159.617976] ------------[ cut here ]------------
[ 159.617987] WARNING: CPU: 3 PID: 5436 at /build/
[ 159.617990] docker_gwbridge: caps=(0x0000008
[ 159.617991] Modules linked in: ip_vs_rr xt_ipvs ip_vs xt_nat xt_tcpudp veth tcp_diag udp_diag inet_diag binfmt_misc vxlan ip6_udp_tunnel udp_tunnel iptable_mangle xt_mark ipt_MASQUERADE nf_nat_
[ 159.618043] aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd psmouse virtio_scsi pata_acpi floppy
[ 159.618053] CPU: 3 PID: 5436 Comm: java Tainted: G W 4.4.0-75-generic #96-Ubuntu
[ 159.618054] Hardware name: Nutanix AHV, BIOS seabios-
[ 159.618056] 0000000000000286 0000000021eefd21 ffff88042d6c3870 ffffffff813f8493
[ 159.618058] ffff88042d6c38b8 ffffffff81d6e7b0 ffff88042d6c38a8 ffffffff81081302
[ 159.618061] ffff880395dbf500 ffff88042a1f0000 0000000000000005 ffff880395dbf500
[ 159.618063] Call Trace:
[ 159.618065] <IRQ> [<ffffffff813f8
[ 159.618075] [<ffffffff81081
[ 159.618077] [<ffffffff81081
[ 159.618081] [<ffffffff813fe
[ 159.618082] [<ffffffff8172e
[ 159.618085] [<ffffffff81732
[ 159.618087] [<ffffffff81732
[ 159.618089] [<ffffffff81733
[ 159.618091] [<ffffffff81733
[ 159.618094] [<ffffffff8173c
[ 159.618099] [<ffffffff81772
[ 159.618104] [<ffffffffc03e0
[ 159.618106] [<ffffffff81773
[ 159.618109] [<ffffffff81767
[ 159.618111] [<ffffffff81774
[ 159.618114] [<ffffffff81773
[ 159.618116] [<ffffffff81770
[ 159.618117] [<ffffffff81770
[ 159.618119] [<ffffffff81770
[ 159.618121] [<ffffffff8176e
[ 159.618123] [<ffffffff8176e
[ 159.618125] [<ffffffff8176e
[ 159.618126] [<ffffffff81730