[Azure] WARNING: CPU: 0 PID: 499 at include/linux/dma-mapping.h:555 netvsc_probe+0x3c9/0x3e0
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux-azure (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Impish |
Fix Released
|
Medium
|
Tim Gardner | ||
Jammy |
Fix Released
|
Medium
|
Tim Gardner |
Bug Description
SRU Justification
[Impact]
When I hot-add a NIC to a Ubuntu 20.04 VM (“5.13.0-1023-azure #27~20.
Please include the March-2022 fix: “Drivers: hv: vmbus: Fix initialization of device object in vmbus_device_
BTW, this call-trace should be harmless to a non-CVM VM.
[ 364.275105] hv_utils: Heartbeat IC version 3.0
[ 364.275137] hv_utils: KVP IC version 4.0
[ 364.275146] hv_utils: Shutdown IC version 3.2
[ 364.275153] hv_utils: TimeSync IC version 4.0
[ 365.281376] ------------[ cut here ]------------
[ 365.281380] WARNING: CPU: 0 PID: 499 at include/
[ 365.281392] Modules linked in: udf crc_itu_t iptable_mangle iptable_filter iptable_raw xt_LOG nf_log_syslog bpfilter nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua kvm_intel kvm joydev hid_generic crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel crypto_simd cryptd serio_raw hv_netvsc pata_acpi hyperv_keyboard hid_hyperv hv_utils hv_balloon hyperv_fb hid sch_fq_codel ipmi_devintf drm ipmi_msghandler msr i2c_core ip_tables x_tables autofs4
[ 365.281422] CPU: 0 PID: 499 Comm: kworker/0:3 Not tainted 5.13.0-1023-azure #27~20.04.1-Ubuntu
[ 365.281424] Hardware name: Microsoft Corporation Virtual Machine/Virtual Machine, BIOS 090008 12/07/2018
[ 365.281427] Workqueue: hv_pri_chan vmbus_add_
[ 365.281434] RIP: 0010:netvsc_
[ 365.281440] Code: 37 c0 4c 89 e6 48 c7 c7 98 f2 37 c0 e8 70 b1 c4 da e9 e9 fc ff ff 49 c7 84 24 88 0b 00 00 00 00 00 00 41 bf f4 ff ff ff eb b0 <0f> 0b e9 19 fe ff ff 41 bf f4 ff ff ff e9 51 ff ff ff 0f 1f 44 00
[ 365.281442] RSP: 0018:ffff992700
[ 365.281444] RAX: 0000000000000000 RBX: ffff890840b21000 RCX: 0000000000000002
[ 365.281446] RDX: 0000000000000002 RSI: 0000000000000000 RDI: 0000000000000002
[ 365.281447] RBP: ffff99270075bbf8 R08: 0000000000000000 R09: 0000000000000000
[ 365.281448] R10: ffffffff9c74e820 R11: 0000000000000394 R12: ffff890844dc6000
[ 365.281449] R13: 0000000000000002 R14: 0000301d0800ae28 R15: 000000000000000f
[ 365.281451] FS: 000000000000000
[ 365.281453] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 365.281454] CR2: 00005619b3504d38 CR3: 00000001091f8005 CR4: 00000000003706f0
[ 365.281459] Call Trace:
[ 365.281461] <TASK>
[ 365.281465] vmbus_probe+
[ 365.281468] really_
[ 365.281472] driver_
[ 365.281476] __device_
[ 365.281479] ? driver_
[ 365.281482] bus_for_
[ 365.281485] __device_
[ 365.281488] device_
[ 365.281491] bus_probe_
[ 365.281494] device_
[ 365.281496] ? hrtimer_
[ 365.281501] device_
[ 365.281503] vmbus_device_
[ 365.281505] vmbus_add_
[ 365.281507] process_
[ 365.281511] worker_
[ 365.281515] ? process_
[ 365.281517] kthread+0x12b/0x150
[ 365.281521] ? set_kthread_
[ 365.281523] ret_from_
[ 365.281528] </TASK>
[ 365.281529] ---[ end trace 80a393e06f0ee58d ]---
[ 365.514764] hv_balloon: Max. dynamic memory size: 8192 MB
[ 367.937000] IPv6: ADDRCONF(
[Test Case]
Microsoft tested
[Where things could go wrong]
CVM VNIC instances may not initialize correctly.
[Other Info]
SF: #00337569
CVE References
affects: | linux (Ubuntu) → linux-azure (Ubuntu) |
Changed in linux-azure (Ubuntu): | |
status: | New → Invalid |
status: | Invalid → Fix Released |
Changed in linux-azure (Ubuntu Impish): | |
assignee: | nobody → Tim Gardner (timg-tpi) |
importance: | Undecided → Medium |
status: | New → In Progress |
Changed in linux-azure (Ubuntu Jammy): | |
assignee: | nobody → Tim Gardner (timg-tpi) |
importance: | Undecided → Medium |
status: | New → In Progress |
Changed in linux-azure (Ubuntu Impish): | |
status: | In Progress → Fix Committed |
Changed in linux-azure (Ubuntu Jammy): | |
status: | In Progress → Fix Committed |
This bug is awaiting verification that the linux-azure/ 5.15.0- 1008.9 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- needed- jammy' to 'verification- done-jammy' . If the problem still exists, change the tag 'verification- needed- jammy' to 'verification- failed- jammy'.
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:/ /wiki.ubuntu. com/Testing/ EnableProposed for documentation how to enable and use -proposed. Thank you!