[Kernel-packages] [Bug 1682561] Re: [Hyper-V] hv: util: move waiting for release to hv_utils_transport itself
This bug was fixed in the package linux - 4.10.0-20.22
---
linux (4.10.0-20.22) zesty; urgency=low
* linux: 4.10.0-20.22 -proposed tracker (LP: #1684491)
* [Hyper-V] hv: util: move waiting for release to hv_utils_transport itself
(LP: #1682561)
- Drivers: hv: util: move waiting for release to hv_utils_transport itself
-- Stefan Bader Wed, 19 Apr 2017 16:13:16
+0200
** Changed in: linux (Ubuntu)
Status: Fix Committed => Fix Released
--
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/1682561
Title:
[Hyper-V] hv: util: move waiting for release to hv_utils_transport
itself
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Xenial:
Fix Released
Status in linux source package in Yakkety:
Fix Released
Status in linux source package in Zesty:
Fix Released
Bug description:
We are observing call traces with the -73 and -74 proposed kernels
that look like this:
[ 240.408061] INFO: task kworker/14:1:179 blocked for more than 120 seconds.
[ 240.412299] Not tainted 4.4.0-73-generic #94-Ubuntu
[ 240.415546] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables
this message.
[ 240.420217] kworker/14:1D 8804e6f23b68 0 179 2
0x
[ 240.420229] Workqueue: hv_vmbus_con vmbus_onmessage_work [hv_vmbus]
[ 240.420236] 8804e6f23b68 000181f9 8804ed944600
8804e6fe3800
[ 240.420241] 8804e6f24000 c0187a48 c0187a40
8804e6fe3800
[ 240.420243] 8804ea196800 8804e6f23b80 81837845
7fff
[ 240.420245] Call Trace:
[ 240.420254] [] schedule+0x35/0x80
[ 240.420256] [] schedule_timeout+0x1b5/0x270
[ 240.420260] [] ? kfree+0x13a/0x150
[ 240.420264] [] ? kfree_const+0x22/0x30
[ 240.420268] [] ? kobject_release+0x94/0x190
[ 240.420270] [] ? kobject_put+0x27/0x50
[ 240.420272] [] wait_for_completion+0xb3/0x140
[ 240.420276] [] ? wake_up_q+0x70/0x70
[ 240.420284] [] hv_kvp_deinit+0x4f/0x60 [hv_utils]
[ 240.420288] [] util_remove+0x21/0x40 [hv_utils]
[ 240.420294] [] vmbus_remove+0x27/0x30 [hv_vmbus]
[ 240.420301] [] __device_release_driver+0xa1/0x150
[ 240.420303] [] device_release_driver+0x23/0x30
[ 240.420306] [] bus_remove_device+0x101/0x170
[ 240.420308] [] device_del+0x139/0x270
[ 240.420310] [] device_unregister+0x1e/0x60
[ 240.420313] [] vmbus_device_unregister+0x1f/0x50
[hv_vmbus]
[ 240.420316] [] vmbus_onoffer_rescind+0x91/0xb0
[hv_vmbus]
[ 240.420324] [] vmbus_onmessage+0x33/0xa0 [hv_vmbus]
[ 240.420327] [] vmbus_onmessage_work+0x21/0x30 [hv_vmbus]
[ 240.420331] [] process_one_work+0x165/0x480
[ 240.420335] [] worker_thread+0x4b/0x4c0
[ 240.420338] [] ? process_one_work+0x480/0x480
[ 240.420341] [] ? process_one_work+0x480/0x480
[ 240.420345] [] kthread+0xd8/0xf0
[ 240.420347] [] ? kthread_create_on_node+0x1e0/0x1e0
[ 240.420350] [] ret_from_fork+0x3f/0x70
[ 240.420352] [] ? kthread_create_on_node+0x1e0/0x1e0
[ 317.360035] serial8250: too much work for irq3
The following commit should fix this issue:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e9c18ae6eb2b312f16c63e34b43ea23926daa398
Waiting for release_event in all three drivers introduced issues on release
as on_reset() hook is not always called. E.g. if the device was never
opened we will never get the completion.
Move the waiting code to hvutil_transport_destroy() and make sure it is
only called when the device is open. hvt->lock serialization should
guarantee the absence of races.
Fixes: 5a66fecbf6aa ("Drivers: hv: util: kvp: Fix a rescind processing issue")
Fixes: 20951c7535b5 ("Drivers: hv: util: Fcopy: Fix a rescind processing
issue")
Fixes: d77044d142e9 ("Drivers: hv: util: Backup: Fix a rescind processing
issue")
Reported-by: Dexuan Cui
Tested-by: Dexuan Cui
Signed-off-by: Vitaly Kuznetsov
Signed-off-by: K. Y. Srinivasan
Signed-off-by: Greg Kroah-Hartman
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1682561/+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 1682561] Re: [Hyper-V] hv: util: move waiting for release to hv_utils_transport itself
This bug was fixed in the package linux - 4.4.0-75.96 --- linux (4.4.0-75.96) xenial; urgency=low * linux: 4.4.0-75.96 -proposed tracker (LP: #1684441) * [Hyper-V] hv: util: move waiting for release to hv_utils_transport itself (LP: #1682561) - Drivers: hv: util: move waiting for release to hv_utils_transport itself linux (4.4.0-74.95) xenial; urgency=low * linux: 4.4.0-74.95 -proposed tracker (LP: #1682041) * [Hyper-V] hv: vmbus: Raise retry/wait limits in vmbus_post_msg() (LP: #1681893) - Drivers: hv: vmbus: Raise retry/wait limits in vmbus_post_msg() linux (4.4.0-73.94) xenial; urgency=low * linux: 4.4.0-73.94 -proposed tracker (LP: #1680416) * CVE-2017-6353 - sctp: deny peeloff operation on asocs with threads sleeping on it * vfat: missing iso8859-1 charset (LP: #1677230) - [Config] NLS_ISO8859_1=y * Regression: KVM modules should be on main kernel package (LP: #1678099) - [Config] powerpc: Add kvm-hv and kvm-pr to the generic inclusion list * linux-lts-xenial 4.4.0-63.84~14.04.2 ADT test failure with linux-lts-xenial 4.4.0-63.84~14.04.2 (LP: #1664912) - SAUCE: apparmor: fix link auditing failure due to, uninitialized var * regession tests failing after stackprofile test is run (LP: #1661030) - SAUCE: fix regression with domain change in complain mode * Permission denied and inconsistent behavior in complain mode with 'ip netns list' command (LP: #1648903) - SAUCE: fix regression with domain change in complain mode * unexpected errno=13 and disconnected path when trying to open /proc/1/ns/mnt from a unshared mount namespace (LP: #1656121) - SAUCE: apparmor: null profiles should inherit parent control flags * apparmor refcount leak of profile namespace when removing profiles (LP: #1660849) - SAUCE: apparmor: fix ns ref count link when removing profiles from policy * tor in lxd: apparmor="DENIED" operation="change_onexec" namespace="root//CONTAINERNAME_" profile="unconfined" name="system_tor" (LP: #1648143) - SAUCE: apparmor: Fix no_new_privs blocking change_onexec when using stacked namespaces * apparmor oops in bind_mnt when dev_path lookup fails (LP: #1660840) - SAUCE: apparmor: fix oops in bind_mnt when dev_path lookup fails * apparmor auditing denied access of special apparmor .null fi\ le (LP: #1660836) - SAUCE: apparmor: Don't audit denied access of special apparmor .null file * apparmor label leak when new label is unused (LP: #1660834) - SAUCE: apparmor: fix label leak when new label is unused * apparmor reference count bug in label_merge_insert() (LP: #1660833) - SAUCE: apparmor: fix reference count bug in label_merge_insert() * apparmor's raw_data file in securityfs is sometimes truncated (LP: #1638996) - SAUCE: apparmor: fix replacement race in reading rawdata * unix domain socket cross permission check failing with nested namespaces (LP: #1660832) - SAUCE: apparmor: fix cross ns perm of unix domain sockets * Xenial update to v4.4.59 stable release (LP: #1678960) - xfrm: policy: init locks early - virtio_balloon: init 1st buffer in stats vq - pinctrl: qcom: Don't clear status bit on irq_unmask - c6x/ptrace: Remove useless PTRACE_SETREGSET implementation - h8300/ptrace: Fix incorrect register transfer count - mips/ptrace: Preserve previous registers for short regset write - sparc/ptrace: Preserve previous registers for short regset write - metag/ptrace: Preserve previous registers for short regset write - metag/ptrace: Provide default TXSTATUS for short NT_PRSTATUS - metag/ptrace: Reject partial NT_METAG_RPIPE writes - fscrypt: remove broken support for detecting keyring key revocation - sched/rt: Add a missing rescheduling point - Linux 4.4.59 * Update ENA driver to 1.1.2 from net-next (LP: #1664312) - net: ena: Remove unnecessary pci_set_drvdata() - net: ena: Fix error return code in ena_device_init() - net: ena: change the return type of ena_set_push_mode() to be void. - net: ena: use setup_timer() and mod_timer() - net/ena: remove ntuple filter support from device feature list - net/ena: fix queues number calculation - net/ena: fix ethtool RSS flow configuration - net/ena: fix RSS default hash configuration - net/ena: fix NULL dereference when removing the driver after device reset failed - net/ena: refactor ena_get_stats64 to be atomic context safe - net/ena: fix potential access to freed memory during device reset - net/ena: use READ_ONCE to access completion descriptors - net/ena: reduce the severity of ena printouts - net/ena: change driver's default timeouts - net/ena: change condition for host attribute configuration - net/ena: update driver version to 1.1.2 * Xenial update to v4.4.58 stable release (LP: #1677600) - net/openvswitch: Set the ipv6 source tunnel key
[Kernel-packages] [Bug 1682561] Re: [Hyper-V] hv: util: move waiting for release to hv_utils_transport itself
This bug was fixed in the package linux - 4.10.0-20.22
---
linux (4.10.0-20.22) zesty; urgency=low
* linux: 4.10.0-20.22 -proposed tracker (LP: #1684491)
* [Hyper-V] hv: util: move waiting for release to hv_utils_transport itself
(LP: #1682561)
- Drivers: hv: util: move waiting for release to hv_utils_transport itself
-- Stefan Bader Wed, 19 Apr 2017 16:13:16
+0200
--
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/1682561
Title:
[Hyper-V] hv: util: move waiting for release to hv_utils_transport
itself
Status in linux package in Ubuntu:
Fix Committed
Status in linux source package in Xenial:
Fix Released
Status in linux source package in Yakkety:
Fix Released
Status in linux source package in Zesty:
Fix Released
Bug description:
We are observing call traces with the -73 and -74 proposed kernels
that look like this:
[ 240.408061] INFO: task kworker/14:1:179 blocked for more than 120 seconds.
[ 240.412299] Not tainted 4.4.0-73-generic #94-Ubuntu
[ 240.415546] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables
this message.
[ 240.420217] kworker/14:1D 8804e6f23b68 0 179 2
0x
[ 240.420229] Workqueue: hv_vmbus_con vmbus_onmessage_work [hv_vmbus]
[ 240.420236] 8804e6f23b68 000181f9 8804ed944600
8804e6fe3800
[ 240.420241] 8804e6f24000 c0187a48 c0187a40
8804e6fe3800
[ 240.420243] 8804ea196800 8804e6f23b80 81837845
7fff
[ 240.420245] Call Trace:
[ 240.420254] [] schedule+0x35/0x80
[ 240.420256] [] schedule_timeout+0x1b5/0x270
[ 240.420260] [] ? kfree+0x13a/0x150
[ 240.420264] [] ? kfree_const+0x22/0x30
[ 240.420268] [] ? kobject_release+0x94/0x190
[ 240.420270] [] ? kobject_put+0x27/0x50
[ 240.420272] [] wait_for_completion+0xb3/0x140
[ 240.420276] [] ? wake_up_q+0x70/0x70
[ 240.420284] [] hv_kvp_deinit+0x4f/0x60 [hv_utils]
[ 240.420288] [] util_remove+0x21/0x40 [hv_utils]
[ 240.420294] [] vmbus_remove+0x27/0x30 [hv_vmbus]
[ 240.420301] [] __device_release_driver+0xa1/0x150
[ 240.420303] [] device_release_driver+0x23/0x30
[ 240.420306] [] bus_remove_device+0x101/0x170
[ 240.420308] [] device_del+0x139/0x270
[ 240.420310] [] device_unregister+0x1e/0x60
[ 240.420313] [] vmbus_device_unregister+0x1f/0x50
[hv_vmbus]
[ 240.420316] [] vmbus_onoffer_rescind+0x91/0xb0
[hv_vmbus]
[ 240.420324] [] vmbus_onmessage+0x33/0xa0 [hv_vmbus]
[ 240.420327] [] vmbus_onmessage_work+0x21/0x30 [hv_vmbus]
[ 240.420331] [] process_one_work+0x165/0x480
[ 240.420335] [] worker_thread+0x4b/0x4c0
[ 240.420338] [] ? process_one_work+0x480/0x480
[ 240.420341] [] ? process_one_work+0x480/0x480
[ 240.420345] [] kthread+0xd8/0xf0
[ 240.420347] [] ? kthread_create_on_node+0x1e0/0x1e0
[ 240.420350] [] ret_from_fork+0x3f/0x70
[ 240.420352] [] ? kthread_create_on_node+0x1e0/0x1e0
[ 317.360035] serial8250: too much work for irq3
The following commit should fix this issue:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e9c18ae6eb2b312f16c63e34b43ea23926daa398
Waiting for release_event in all three drivers introduced issues on release
as on_reset() hook is not always called. E.g. if the device was never
opened we will never get the completion.
Move the waiting code to hvutil_transport_destroy() and make sure it is
only called when the device is open. hvt->lock serialization should
guarantee the absence of races.
Fixes: 5a66fecbf6aa ("Drivers: hv: util: kvp: Fix a rescind processing issue")
Fixes: 20951c7535b5 ("Drivers: hv: util: Fcopy: Fix a rescind processing
issue")
Fixes: d77044d142e9 ("Drivers: hv: util: Backup: Fix a rescind processing
issue")
Reported-by: Dexuan Cui
Tested-by: Dexuan Cui
Signed-off-by: Vitaly Kuznetsov
Signed-off-by: K. Y. Srinivasan
Signed-off-by: Greg Kroah-Hartman
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1682561/+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 1682561] Re: [Hyper-V] hv: util: move waiting for release to hv_utils_transport itself
This bug was fixed in the package linux - 4.8.0-49.52 --- linux (4.8.0-49.52) yakkety; urgency=low * linux: 4.8.0-49.52 -proposed tracker (LP: #1684427) * [Hyper-V] hv: util: move waiting for release to hv_utils_transport itself (LP: #1682561) - Drivers: hv: util: move waiting for release to hv_utils_transport itself linux (4.8.0-48.51) yakkety; urgency=low * linux: 4.8.0-48.51 -proposed tracker (LP: #1682034) * [Hyper-V] hv: vmbus: Raise retry/wait limits in vmbus_post_msg() (LP: #1681893) - Drivers: hv: vmbus: Raise retry/wait limits in vmbus_post_msg() linux (4.8.0-47.50) yakkety; urgency=low * linux: 4.8.0-47.50 -proposed tracker (LP: #1679678) * CVE-2017-6353 - sctp: deny peeloff operation on asocs with threads sleeping on it * CVE-2017-5986 - sctp: avoid BUG_ON on sctp_wait_for_sndbuf * vfat: missing iso8859-1 charset (LP: #1677230) - [Config] NLS_ISO8859_1=y * [Hyper-V] pci-hyperv: Use device serial number as PCI domain (LP: #1667527) - net/mlx4_core: Use cq quota in SRIOV when creating completion EQs * Regression: KVM modules should be on main kernel package (LP: #1678099) - [Config] powerpc: Add kvm-hv and kvm-pr to the generic inclusion list * linux-lts-xenial 4.4.0-63.84~14.04.2 ADT test failure with linux-lts-xenial 4.4.0-63.84~14.04.2 (LP: #1664912) - SAUCE: apparmor: fix link auditing failure due to, uninitialized var * regession tests failing after stackprofile test is run (LP: #1661030) - SAUCE: fix regression with domain change in complain mode * Permission denied and inconsistent behavior in complain mode with 'ip netns list' command (LP: #1648903) - SAUCE: fix regression with domain change in complain mode * unexpected errno=13 and disconnected path when trying to open /proc/1/ns/mnt from a unshared mount namespace (LP: #1656121) - SAUCE: apparmor: null profiles should inherit parent control flags * apparmor refcount leak of profile namespace when removing profiles (LP: #1660849) - SAUCE: apparmor: fix ns ref count link when removing profiles from policy * tor in lxd: apparmor="DENIED" operation="change_onexec" namespace="root//CONTAINERNAME_" profile="unconfined" name="system_tor" (LP: #1648143) - SAUCE: apparmor: Fix no_new_privs blocking change_onexec when using stacked namespaces * apparmor oops in bind_mnt when dev_path lookup fails (LP: #1660840) - SAUCE: apparmor: fix oops in bind_mnt when dev_path lookup fails * apparmor auditing denied access of special apparmor .null fi\ le (LP: #1660836) - SAUCE: apparmor: Don't audit denied access of special apparmor .null file * apparmor label leak when new label is unused (LP: #1660834) - SAUCE: apparmor: fix label leak when new label is unused * apparmor reference count bug in label_merge_insert() (LP: #1660833) - SAUCE: apparmor: fix reference count bug in label_merge_insert() * apparmor's raw_data file in securityfs is sometimes truncated (LP: #1638996) - SAUCE: apparmor: fix replacement race in reading rawdata * unix domain socket cross permission check failing with nested namespaces (LP: #1660832) - SAUCE: apparmor: fix cross ns perm of unix domain sockets * [Hyper-V][Mellanox] net/mlx4_core: Avoid delays during VF driver device shutdown (LP: #1672785) - Revert "net/mlx4_en: Avoid unregister_netdev at shutdown flow" - net/mlx4_core: Avoid delays during VF driver device shutdown * Update ENA driver to 1.1.2 from net-next (LP: #1664312) - net: ena: Remove unnecessary pci_set_drvdata() - net: ena: Fix error return code in ena_device_init() - net: ena: change the return type of ena_set_push_mode() to be void. - net: ena: use setup_timer() and mod_timer() - net/ena: remove ntuple filter support from device feature list - net/ena: fix queues number calculation - net/ena: fix ethtool RSS flow configuration - net/ena: fix RSS default hash configuration - net/ena: fix NULL dereference when removing the driver after device reset failed - net/ena: refactor ena_get_stats64 to be atomic context safe - net/ena: fix potential access to freed memory during device reset - net/ena: use READ_ONCE to access completion descriptors - net/ena: reduce the severity of ena printouts - net/ena: change driver's default timeouts - net/ena: change condition for host attribute configuration - net/ena: update driver version to 1.1.2 * ISST-LTE:pVM:roselp4:ubuntu16.04.2: number of numa_miss and numa_foreign wrong in numastat (LP: #1672953) - mm: fix remote numa hits statistics - mm: get rid of __GFP_OTHER_NODE * Using an NVMe drive causes huge power drain (LP: #1664602) - nvme/scsi: Remove power management support - nvme: Pass pointers, not dma addresses, to nvme_get/set_features() - nvme: introduce struct nvme_request - nvme: Add a quirk mechanis
[Kernel-packages] [Bug 1682561] Re: [Hyper-V] hv: util: move waiting for release to hv_utils_transport itself
Thanks! We'll verify the fix in -proposed.
--
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/1682561
Title:
[Hyper-V] hv: util: move waiting for release to hv_utils_transport
itself
Status in linux package in Ubuntu:
Fix Committed
Status in linux source package in Xenial:
Fix Committed
Status in linux source package in Yakkety:
Fix Committed
Status in linux source package in Zesty:
Fix Committed
Bug description:
We are observing call traces with the -73 and -74 proposed kernels
that look like this:
[ 240.408061] INFO: task kworker/14:1:179 blocked for more than 120 seconds.
[ 240.412299] Not tainted 4.4.0-73-generic #94-Ubuntu
[ 240.415546] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables
this message.
[ 240.420217] kworker/14:1D 8804e6f23b68 0 179 2
0x
[ 240.420229] Workqueue: hv_vmbus_con vmbus_onmessage_work [hv_vmbus]
[ 240.420236] 8804e6f23b68 000181f9 8804ed944600
8804e6fe3800
[ 240.420241] 8804e6f24000 c0187a48 c0187a40
8804e6fe3800
[ 240.420243] 8804ea196800 8804e6f23b80 81837845
7fff
[ 240.420245] Call Trace:
[ 240.420254] [] schedule+0x35/0x80
[ 240.420256] [] schedule_timeout+0x1b5/0x270
[ 240.420260] [] ? kfree+0x13a/0x150
[ 240.420264] [] ? kfree_const+0x22/0x30
[ 240.420268] [] ? kobject_release+0x94/0x190
[ 240.420270] [] ? kobject_put+0x27/0x50
[ 240.420272] [] wait_for_completion+0xb3/0x140
[ 240.420276] [] ? wake_up_q+0x70/0x70
[ 240.420284] [] hv_kvp_deinit+0x4f/0x60 [hv_utils]
[ 240.420288] [] util_remove+0x21/0x40 [hv_utils]
[ 240.420294] [] vmbus_remove+0x27/0x30 [hv_vmbus]
[ 240.420301] [] __device_release_driver+0xa1/0x150
[ 240.420303] [] device_release_driver+0x23/0x30
[ 240.420306] [] bus_remove_device+0x101/0x170
[ 240.420308] [] device_del+0x139/0x270
[ 240.420310] [] device_unregister+0x1e/0x60
[ 240.420313] [] vmbus_device_unregister+0x1f/0x50
[hv_vmbus]
[ 240.420316] [] vmbus_onoffer_rescind+0x91/0xb0
[hv_vmbus]
[ 240.420324] [] vmbus_onmessage+0x33/0xa0 [hv_vmbus]
[ 240.420327] [] vmbus_onmessage_work+0x21/0x30 [hv_vmbus]
[ 240.420331] [] process_one_work+0x165/0x480
[ 240.420335] [] worker_thread+0x4b/0x4c0
[ 240.420338] [] ? process_one_work+0x480/0x480
[ 240.420341] [] ? process_one_work+0x480/0x480
[ 240.420345] [] kthread+0xd8/0xf0
[ 240.420347] [] ? kthread_create_on_node+0x1e0/0x1e0
[ 240.420350] [] ret_from_fork+0x3f/0x70
[ 240.420352] [] ? kthread_create_on_node+0x1e0/0x1e0
[ 317.360035] serial8250: too much work for irq3
The following commit should fix this issue:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e9c18ae6eb2b312f16c63e34b43ea23926daa398
Waiting for release_event in all three drivers introduced issues on release
as on_reset() hook is not always called. E.g. if the device was never
opened we will never get the completion.
Move the waiting code to hvutil_transport_destroy() and make sure it is
only called when the device is open. hvt->lock serialization should
guarantee the absence of races.
Fixes: 5a66fecbf6aa ("Drivers: hv: util: kvp: Fix a rescind processing issue")
Fixes: 20951c7535b5 ("Drivers: hv: util: Fcopy: Fix a rescind processing
issue")
Fixes: d77044d142e9 ("Drivers: hv: util: Backup: Fix a rescind processing
issue")
Reported-by: Dexuan Cui
Tested-by: Dexuan Cui
Signed-off-by: Vitaly Kuznetsov
Signed-off-by: K. Y. Srinivasan
Signed-off-by: Greg Kroah-Hartman
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1682561/+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 1682561] Re: [Hyper-V] hv: util: move waiting for release to hv_utils_transport itself
** Changed in: linux (Ubuntu Zesty)
Status: In Progress => Fix Committed
** Changed in: linux (Ubuntu Xenial)
Status: In Progress => Fix Committed
** Changed in: linux (Ubuntu Yakkety)
Status: In Progress => Fix Committed
--
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/1682561
Title:
[Hyper-V] hv: util: move waiting for release to hv_utils_transport
itself
Status in linux package in Ubuntu:
Fix Committed
Status in linux source package in Xenial:
Fix Committed
Status in linux source package in Yakkety:
Fix Committed
Status in linux source package in Zesty:
Fix Committed
Bug description:
We are observing call traces with the -73 and -74 proposed kernels
that look like this:
[ 240.408061] INFO: task kworker/14:1:179 blocked for more than 120 seconds.
[ 240.412299] Not tainted 4.4.0-73-generic #94-Ubuntu
[ 240.415546] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables
this message.
[ 240.420217] kworker/14:1D 8804e6f23b68 0 179 2
0x
[ 240.420229] Workqueue: hv_vmbus_con vmbus_onmessage_work [hv_vmbus]
[ 240.420236] 8804e6f23b68 000181f9 8804ed944600
8804e6fe3800
[ 240.420241] 8804e6f24000 c0187a48 c0187a40
8804e6fe3800
[ 240.420243] 8804ea196800 8804e6f23b80 81837845
7fff
[ 240.420245] Call Trace:
[ 240.420254] [] schedule+0x35/0x80
[ 240.420256] [] schedule_timeout+0x1b5/0x270
[ 240.420260] [] ? kfree+0x13a/0x150
[ 240.420264] [] ? kfree_const+0x22/0x30
[ 240.420268] [] ? kobject_release+0x94/0x190
[ 240.420270] [] ? kobject_put+0x27/0x50
[ 240.420272] [] wait_for_completion+0xb3/0x140
[ 240.420276] [] ? wake_up_q+0x70/0x70
[ 240.420284] [] hv_kvp_deinit+0x4f/0x60 [hv_utils]
[ 240.420288] [] util_remove+0x21/0x40 [hv_utils]
[ 240.420294] [] vmbus_remove+0x27/0x30 [hv_vmbus]
[ 240.420301] [] __device_release_driver+0xa1/0x150
[ 240.420303] [] device_release_driver+0x23/0x30
[ 240.420306] [] bus_remove_device+0x101/0x170
[ 240.420308] [] device_del+0x139/0x270
[ 240.420310] [] device_unregister+0x1e/0x60
[ 240.420313] [] vmbus_device_unregister+0x1f/0x50
[hv_vmbus]
[ 240.420316] [] vmbus_onoffer_rescind+0x91/0xb0
[hv_vmbus]
[ 240.420324] [] vmbus_onmessage+0x33/0xa0 [hv_vmbus]
[ 240.420327] [] vmbus_onmessage_work+0x21/0x30 [hv_vmbus]
[ 240.420331] [] process_one_work+0x165/0x480
[ 240.420335] [] worker_thread+0x4b/0x4c0
[ 240.420338] [] ? process_one_work+0x480/0x480
[ 240.420341] [] ? process_one_work+0x480/0x480
[ 240.420345] [] kthread+0xd8/0xf0
[ 240.420347] [] ? kthread_create_on_node+0x1e0/0x1e0
[ 240.420350] [] ret_from_fork+0x3f/0x70
[ 240.420352] [] ? kthread_create_on_node+0x1e0/0x1e0
[ 317.360035] serial8250: too much work for irq3
The following commit should fix this issue:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e9c18ae6eb2b312f16c63e34b43ea23926daa398
Waiting for release_event in all three drivers introduced issues on release
as on_reset() hook is not always called. E.g. if the device was never
opened we will never get the completion.
Move the waiting code to hvutil_transport_destroy() and make sure it is
only called when the device is open. hvt->lock serialization should
guarantee the absence of races.
Fixes: 5a66fecbf6aa ("Drivers: hv: util: kvp: Fix a rescind processing issue")
Fixes: 20951c7535b5 ("Drivers: hv: util: Fcopy: Fix a rescind processing
issue")
Fixes: d77044d142e9 ("Drivers: hv: util: Backup: Fix a rescind processing
issue")
Reported-by: Dexuan Cui
Tested-by: Dexuan Cui
Signed-off-by: Vitaly Kuznetsov
Signed-off-by: K. Y. Srinivasan
Signed-off-by: Greg Kroah-Hartman
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1682561/+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 1682561] Re: [Hyper-V] hv: util: move waiting for release to hv_utils_transport itself
Thanks for the feedback, Josh.
SRU requests submitted:
https://lists.ubuntu.com/archives/kernel-team/2017-April/083633.html
https://lists.ubuntu.com/archives/kernel-team/2017-April/083635.html
--
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/1682561
Title:
[Hyper-V] hv: util: move waiting for release to hv_utils_transport
itself
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Xenial:
In Progress
Status in linux source package in Yakkety:
In Progress
Status in linux source package in Zesty:
In Progress
Bug description:
We are observing call traces with the -73 and -74 proposed kernels
that look like this:
[ 240.408061] INFO: task kworker/14:1:179 blocked for more than 120 seconds.
[ 240.412299] Not tainted 4.4.0-73-generic #94-Ubuntu
[ 240.415546] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables
this message.
[ 240.420217] kworker/14:1D 8804e6f23b68 0 179 2
0x
[ 240.420229] Workqueue: hv_vmbus_con vmbus_onmessage_work [hv_vmbus]
[ 240.420236] 8804e6f23b68 000181f9 8804ed944600
8804e6fe3800
[ 240.420241] 8804e6f24000 c0187a48 c0187a40
8804e6fe3800
[ 240.420243] 8804ea196800 8804e6f23b80 81837845
7fff
[ 240.420245] Call Trace:
[ 240.420254] [] schedule+0x35/0x80
[ 240.420256] [] schedule_timeout+0x1b5/0x270
[ 240.420260] [] ? kfree+0x13a/0x150
[ 240.420264] [] ? kfree_const+0x22/0x30
[ 240.420268] [] ? kobject_release+0x94/0x190
[ 240.420270] [] ? kobject_put+0x27/0x50
[ 240.420272] [] wait_for_completion+0xb3/0x140
[ 240.420276] [] ? wake_up_q+0x70/0x70
[ 240.420284] [] hv_kvp_deinit+0x4f/0x60 [hv_utils]
[ 240.420288] [] util_remove+0x21/0x40 [hv_utils]
[ 240.420294] [] vmbus_remove+0x27/0x30 [hv_vmbus]
[ 240.420301] [] __device_release_driver+0xa1/0x150
[ 240.420303] [] device_release_driver+0x23/0x30
[ 240.420306] [] bus_remove_device+0x101/0x170
[ 240.420308] [] device_del+0x139/0x270
[ 240.420310] [] device_unregister+0x1e/0x60
[ 240.420313] [] vmbus_device_unregister+0x1f/0x50
[hv_vmbus]
[ 240.420316] [] vmbus_onoffer_rescind+0x91/0xb0
[hv_vmbus]
[ 240.420324] [] vmbus_onmessage+0x33/0xa0 [hv_vmbus]
[ 240.420327] [] vmbus_onmessage_work+0x21/0x30 [hv_vmbus]
[ 240.420331] [] process_one_work+0x165/0x480
[ 240.420335] [] worker_thread+0x4b/0x4c0
[ 240.420338] [] ? process_one_work+0x480/0x480
[ 240.420341] [] ? process_one_work+0x480/0x480
[ 240.420345] [] kthread+0xd8/0xf0
[ 240.420347] [] ? kthread_create_on_node+0x1e0/0x1e0
[ 240.420350] [] ret_from_fork+0x3f/0x70
[ 240.420352] [] ? kthread_create_on_node+0x1e0/0x1e0
[ 317.360035] serial8250: too much work for irq3
The following commit should fix this issue:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e9c18ae6eb2b312f16c63e34b43ea23926daa398
Waiting for release_event in all three drivers introduced issues on release
as on_reset() hook is not always called. E.g. if the device was never
opened we will never get the completion.
Move the waiting code to hvutil_transport_destroy() and make sure it is
only called when the device is open. hvt->lock serialization should
guarantee the absence of races.
Fixes: 5a66fecbf6aa ("Drivers: hv: util: kvp: Fix a rescind processing issue")
Fixes: 20951c7535b5 ("Drivers: hv: util: Fcopy: Fix a rescind processing
issue")
Fixes: d77044d142e9 ("Drivers: hv: util: Backup: Fix a rescind processing
issue")
Reported-by: Dexuan Cui
Tested-by: Dexuan Cui
Signed-off-by: Vitaly Kuznetsov
Signed-off-by: K. Y. Srinivasan
Signed-off-by: Greg Kroah-Hartman
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1682561/+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 1682561] Re: [Hyper-V] hv: util: move waiting for release to hv_utils_transport itself
Those commits are in the payload for
https://bugs.launchpad.net/ubuntu/xenial/+source/linux/+bug/1670544
which is in proposed right now.
--
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/1682561
Title:
[Hyper-V] hv: util: move waiting for release to hv_utils_transport
itself
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Xenial:
In Progress
Status in linux source package in Yakkety:
In Progress
Status in linux source package in Zesty:
In Progress
Bug description:
We are observing call traces with the -73 and -74 proposed kernels
that look like this:
[ 240.408061] INFO: task kworker/14:1:179 blocked for more than 120 seconds.
[ 240.412299] Not tainted 4.4.0-73-generic #94-Ubuntu
[ 240.415546] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables
this message.
[ 240.420217] kworker/14:1D 8804e6f23b68 0 179 2
0x
[ 240.420229] Workqueue: hv_vmbus_con vmbus_onmessage_work [hv_vmbus]
[ 240.420236] 8804e6f23b68 000181f9 8804ed944600
8804e6fe3800
[ 240.420241] 8804e6f24000 c0187a48 c0187a40
8804e6fe3800
[ 240.420243] 8804ea196800 8804e6f23b80 81837845
7fff
[ 240.420245] Call Trace:
[ 240.420254] [] schedule+0x35/0x80
[ 240.420256] [] schedule_timeout+0x1b5/0x270
[ 240.420260] [] ? kfree+0x13a/0x150
[ 240.420264] [] ? kfree_const+0x22/0x30
[ 240.420268] [] ? kobject_release+0x94/0x190
[ 240.420270] [] ? kobject_put+0x27/0x50
[ 240.420272] [] wait_for_completion+0xb3/0x140
[ 240.420276] [] ? wake_up_q+0x70/0x70
[ 240.420284] [] hv_kvp_deinit+0x4f/0x60 [hv_utils]
[ 240.420288] [] util_remove+0x21/0x40 [hv_utils]
[ 240.420294] [] vmbus_remove+0x27/0x30 [hv_vmbus]
[ 240.420301] [] __device_release_driver+0xa1/0x150
[ 240.420303] [] device_release_driver+0x23/0x30
[ 240.420306] [] bus_remove_device+0x101/0x170
[ 240.420308] [] device_del+0x139/0x270
[ 240.420310] [] device_unregister+0x1e/0x60
[ 240.420313] [] vmbus_device_unregister+0x1f/0x50
[hv_vmbus]
[ 240.420316] [] vmbus_onoffer_rescind+0x91/0xb0
[hv_vmbus]
[ 240.420324] [] vmbus_onmessage+0x33/0xa0 [hv_vmbus]
[ 240.420327] [] vmbus_onmessage_work+0x21/0x30 [hv_vmbus]
[ 240.420331] [] process_one_work+0x165/0x480
[ 240.420335] [] worker_thread+0x4b/0x4c0
[ 240.420338] [] ? process_one_work+0x480/0x480
[ 240.420341] [] ? process_one_work+0x480/0x480
[ 240.420345] [] kthread+0xd8/0xf0
[ 240.420347] [] ? kthread_create_on_node+0x1e0/0x1e0
[ 240.420350] [] ret_from_fork+0x3f/0x70
[ 240.420352] [] ? kthread_create_on_node+0x1e0/0x1e0
[ 317.360035] serial8250: too much work for irq3
The following commit should fix this issue:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e9c18ae6eb2b312f16c63e34b43ea23926daa398
Waiting for release_event in all three drivers introduced issues on release
as on_reset() hook is not always called. E.g. if the device was never
opened we will never get the completion.
Move the waiting code to hvutil_transport_destroy() and make sure it is
only called when the device is open. hvt->lock serialization should
guarantee the absence of races.
Fixes: 5a66fecbf6aa ("Drivers: hv: util: kvp: Fix a rescind processing issue")
Fixes: 20951c7535b5 ("Drivers: hv: util: Fcopy: Fix a rescind processing
issue")
Fixes: d77044d142e9 ("Drivers: hv: util: Backup: Fix a rescind processing
issue")
Reported-by: Dexuan Cui
Tested-by: Dexuan Cui
Signed-off-by: Vitaly Kuznetsov
Signed-off-by: K. Y. Srinivasan
Signed-off-by: Greg Kroah-Hartman
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1682561/+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 1682561] Re: [Hyper-V] hv: util: move waiting for release to hv_utils_transport itself
The three commits that introduced this bug have not landed in
Yakkety(4.8). That's because 4.8 is EOL upstream and no longer gets
upstream stable updates.
Will yakkety still needed commit e9c18ae6eb2b? The requested commit applied
and built fine.
Yakkety will not get the following three updates unless they come in from
another Ubuntu specific bug, which I don't think exists:
- Drivers: hv: util: kvp: Fix a rescind processing issue
- Drivers: hv: util: Fcopy: Fix a rescind processing issue
- Drivers: hv: util: Backup: Fix a rescind processing issue
--
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/1682561
Title:
[Hyper-V] hv: util: move waiting for release to hv_utils_transport
itself
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Xenial:
In Progress
Status in linux source package in Yakkety:
In Progress
Status in linux source package in Zesty:
In Progress
Bug description:
We are observing call traces with the -73 and -74 proposed kernels
that look like this:
[ 240.408061] INFO: task kworker/14:1:179 blocked for more than 120 seconds.
[ 240.412299] Not tainted 4.4.0-73-generic #94-Ubuntu
[ 240.415546] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables
this message.
[ 240.420217] kworker/14:1D 8804e6f23b68 0 179 2
0x
[ 240.420229] Workqueue: hv_vmbus_con vmbus_onmessage_work [hv_vmbus]
[ 240.420236] 8804e6f23b68 000181f9 8804ed944600
8804e6fe3800
[ 240.420241] 8804e6f24000 c0187a48 c0187a40
8804e6fe3800
[ 240.420243] 8804ea196800 8804e6f23b80 81837845
7fff
[ 240.420245] Call Trace:
[ 240.420254] [] schedule+0x35/0x80
[ 240.420256] [] schedule_timeout+0x1b5/0x270
[ 240.420260] [] ? kfree+0x13a/0x150
[ 240.420264] [] ? kfree_const+0x22/0x30
[ 240.420268] [] ? kobject_release+0x94/0x190
[ 240.420270] [] ? kobject_put+0x27/0x50
[ 240.420272] [] wait_for_completion+0xb3/0x140
[ 240.420276] [] ? wake_up_q+0x70/0x70
[ 240.420284] [] hv_kvp_deinit+0x4f/0x60 [hv_utils]
[ 240.420288] [] util_remove+0x21/0x40 [hv_utils]
[ 240.420294] [] vmbus_remove+0x27/0x30 [hv_vmbus]
[ 240.420301] [] __device_release_driver+0xa1/0x150
[ 240.420303] [] device_release_driver+0x23/0x30
[ 240.420306] [] bus_remove_device+0x101/0x170
[ 240.420308] [] device_del+0x139/0x270
[ 240.420310] [] device_unregister+0x1e/0x60
[ 240.420313] [] vmbus_device_unregister+0x1f/0x50
[hv_vmbus]
[ 240.420316] [] vmbus_onoffer_rescind+0x91/0xb0
[hv_vmbus]
[ 240.420324] [] vmbus_onmessage+0x33/0xa0 [hv_vmbus]
[ 240.420327] [] vmbus_onmessage_work+0x21/0x30 [hv_vmbus]
[ 240.420331] [] process_one_work+0x165/0x480
[ 240.420335] [] worker_thread+0x4b/0x4c0
[ 240.420338] [] ? process_one_work+0x480/0x480
[ 240.420341] [] ? process_one_work+0x480/0x480
[ 240.420345] [] kthread+0xd8/0xf0
[ 240.420347] [] ? kthread_create_on_node+0x1e0/0x1e0
[ 240.420350] [] ret_from_fork+0x3f/0x70
[ 240.420352] [] ? kthread_create_on_node+0x1e0/0x1e0
[ 317.360035] serial8250: too much work for irq3
The following commit should fix this issue:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e9c18ae6eb2b312f16c63e34b43ea23926daa398
Waiting for release_event in all three drivers introduced issues on release
as on_reset() hook is not always called. E.g. if the device was never
opened we will never get the completion.
Move the waiting code to hvutil_transport_destroy() and make sure it is
only called when the device is open. hvt->lock serialization should
guarantee the absence of races.
Fixes: 5a66fecbf6aa ("Drivers: hv: util: kvp: Fix a rescind processing issue")
Fixes: 20951c7535b5 ("Drivers: hv: util: Fcopy: Fix a rescind processing
issue")
Fixes: d77044d142e9 ("Drivers: hv: util: Backup: Fix a rescind processing
issue")
Reported-by: Dexuan Cui
Tested-by: Dexuan Cui
Signed-off-by: Vitaly Kuznetsov
Signed-off-by: K. Y. Srinivasan
Signed-off-by: Greg Kroah-Hartman
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1682561/+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 1682561] Re: [Hyper-V] hv: util: move waiting for release to hv_utils_transport itself
It is fixed in the test kernel http://kernel.ubuntu.com/~jsalisbury/lp1682561/.
Please submit the SRU request.
--
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/1682561
Title:
[Hyper-V] hv: util: move waiting for release to hv_utils_transport
itself
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Xenial:
In Progress
Status in linux source package in Yakkety:
In Progress
Status in linux source package in Zesty:
In Progress
Bug description:
We are observing call traces with the -73 and -74 proposed kernels
that look like this:
[ 240.408061] INFO: task kworker/14:1:179 blocked for more than 120 seconds.
[ 240.412299] Not tainted 4.4.0-73-generic #94-Ubuntu
[ 240.415546] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables
this message.
[ 240.420217] kworker/14:1D 8804e6f23b68 0 179 2
0x
[ 240.420229] Workqueue: hv_vmbus_con vmbus_onmessage_work [hv_vmbus]
[ 240.420236] 8804e6f23b68 000181f9 8804ed944600
8804e6fe3800
[ 240.420241] 8804e6f24000 c0187a48 c0187a40
8804e6fe3800
[ 240.420243] 8804ea196800 8804e6f23b80 81837845
7fff
[ 240.420245] Call Trace:
[ 240.420254] [] schedule+0x35/0x80
[ 240.420256] [] schedule_timeout+0x1b5/0x270
[ 240.420260] [] ? kfree+0x13a/0x150
[ 240.420264] [] ? kfree_const+0x22/0x30
[ 240.420268] [] ? kobject_release+0x94/0x190
[ 240.420270] [] ? kobject_put+0x27/0x50
[ 240.420272] [] wait_for_completion+0xb3/0x140
[ 240.420276] [] ? wake_up_q+0x70/0x70
[ 240.420284] [] hv_kvp_deinit+0x4f/0x60 [hv_utils]
[ 240.420288] [] util_remove+0x21/0x40 [hv_utils]
[ 240.420294] [] vmbus_remove+0x27/0x30 [hv_vmbus]
[ 240.420301] [] __device_release_driver+0xa1/0x150
[ 240.420303] [] device_release_driver+0x23/0x30
[ 240.420306] [] bus_remove_device+0x101/0x170
[ 240.420308] [] device_del+0x139/0x270
[ 240.420310] [] device_unregister+0x1e/0x60
[ 240.420313] [] vmbus_device_unregister+0x1f/0x50
[hv_vmbus]
[ 240.420316] [] vmbus_onoffer_rescind+0x91/0xb0
[hv_vmbus]
[ 240.420324] [] vmbus_onmessage+0x33/0xa0 [hv_vmbus]
[ 240.420327] [] vmbus_onmessage_work+0x21/0x30 [hv_vmbus]
[ 240.420331] [] process_one_work+0x165/0x480
[ 240.420335] [] worker_thread+0x4b/0x4c0
[ 240.420338] [] ? process_one_work+0x480/0x480
[ 240.420341] [] ? process_one_work+0x480/0x480
[ 240.420345] [] kthread+0xd8/0xf0
[ 240.420347] [] ? kthread_create_on_node+0x1e0/0x1e0
[ 240.420350] [] ret_from_fork+0x3f/0x70
[ 240.420352] [] ? kthread_create_on_node+0x1e0/0x1e0
[ 317.360035] serial8250: too much work for irq3
The following commit should fix this issue:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e9c18ae6eb2b312f16c63e34b43ea23926daa398
Waiting for release_event in all three drivers introduced issues on release
as on_reset() hook is not always called. E.g. if the device was never
opened we will never get the completion.
Move the waiting code to hvutil_transport_destroy() and make sure it is
only called when the device is open. hvt->lock serialization should
guarantee the absence of races.
Fixes: 5a66fecbf6aa ("Drivers: hv: util: kvp: Fix a rescind processing issue")
Fixes: 20951c7535b5 ("Drivers: hv: util: Fcopy: Fix a rescind processing
issue")
Fixes: d77044d142e9 ("Drivers: hv: util: Backup: Fix a rescind processing
issue")
Reported-by: Dexuan Cui
Tested-by: Dexuan Cui
Signed-off-by: Vitaly Kuznetsov
Signed-off-by: K. Y. Srinivasan
Signed-off-by: Greg Kroah-Hartman
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1682561/+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 1682561] Re: [Hyper-V] hv: util: move waiting for release to hv_utils_transport itself
I built a test kernel with a pick of commit e9c18ae6eb2b. It can be downloaded
from:
http://kernel.ubuntu.com/~jsalisbury/lp1682561/
I'll submit an SRU request as soon as it's confirmed a fix for the bug.
--
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/1682561
Title:
[Hyper-V] hv: util: move waiting for release to hv_utils_transport
itself
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Xenial:
In Progress
Status in linux source package in Yakkety:
In Progress
Status in linux source package in Zesty:
In Progress
Bug description:
We are observing call traces with the -73 and -74 proposed kernels
that look like this:
[ 240.408061] INFO: task kworker/14:1:179 blocked for more than 120 seconds.
[ 240.412299] Not tainted 4.4.0-73-generic #94-Ubuntu
[ 240.415546] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables
this message.
[ 240.420217] kworker/14:1D 8804e6f23b68 0 179 2
0x
[ 240.420229] Workqueue: hv_vmbus_con vmbus_onmessage_work [hv_vmbus]
[ 240.420236] 8804e6f23b68 000181f9 8804ed944600
8804e6fe3800
[ 240.420241] 8804e6f24000 c0187a48 c0187a40
8804e6fe3800
[ 240.420243] 8804ea196800 8804e6f23b80 81837845
7fff
[ 240.420245] Call Trace:
[ 240.420254] [] schedule+0x35/0x80
[ 240.420256] [] schedule_timeout+0x1b5/0x270
[ 240.420260] [] ? kfree+0x13a/0x150
[ 240.420264] [] ? kfree_const+0x22/0x30
[ 240.420268] [] ? kobject_release+0x94/0x190
[ 240.420270] [] ? kobject_put+0x27/0x50
[ 240.420272] [] wait_for_completion+0xb3/0x140
[ 240.420276] [] ? wake_up_q+0x70/0x70
[ 240.420284] [] hv_kvp_deinit+0x4f/0x60 [hv_utils]
[ 240.420288] [] util_remove+0x21/0x40 [hv_utils]
[ 240.420294] [] vmbus_remove+0x27/0x30 [hv_vmbus]
[ 240.420301] [] __device_release_driver+0xa1/0x150
[ 240.420303] [] device_release_driver+0x23/0x30
[ 240.420306] [] bus_remove_device+0x101/0x170
[ 240.420308] [] device_del+0x139/0x270
[ 240.420310] [] device_unregister+0x1e/0x60
[ 240.420313] [] vmbus_device_unregister+0x1f/0x50
[hv_vmbus]
[ 240.420316] [] vmbus_onoffer_rescind+0x91/0xb0
[hv_vmbus]
[ 240.420324] [] vmbus_onmessage+0x33/0xa0 [hv_vmbus]
[ 240.420327] [] vmbus_onmessage_work+0x21/0x30 [hv_vmbus]
[ 240.420331] [] process_one_work+0x165/0x480
[ 240.420335] [] worker_thread+0x4b/0x4c0
[ 240.420338] [] ? process_one_work+0x480/0x480
[ 240.420341] [] ? process_one_work+0x480/0x480
[ 240.420345] [] kthread+0xd8/0xf0
[ 240.420347] [] ? kthread_create_on_node+0x1e0/0x1e0
[ 240.420350] [] ret_from_fork+0x3f/0x70
[ 240.420352] [] ? kthread_create_on_node+0x1e0/0x1e0
[ 317.360035] serial8250: too much work for irq3
The following commit should fix this issue:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e9c18ae6eb2b312f16c63e34b43ea23926daa398
Waiting for release_event in all three drivers introduced issues on release
as on_reset() hook is not always called. E.g. if the device was never
opened we will never get the completion.
Move the waiting code to hvutil_transport_destroy() and make sure it is
only called when the device is open. hvt->lock serialization should
guarantee the absence of races.
Fixes: 5a66fecbf6aa ("Drivers: hv: util: kvp: Fix a rescind processing issue")
Fixes: 20951c7535b5 ("Drivers: hv: util: Fcopy: Fix a rescind processing
issue")
Fixes: d77044d142e9 ("Drivers: hv: util: Backup: Fix a rescind processing
issue")
Reported-by: Dexuan Cui
Tested-by: Dexuan Cui
Signed-off-by: Vitaly Kuznetsov
Signed-off-by: K. Y. Srinivasan
Signed-off-by: Greg Kroah-Hartman
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1682561/+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 1682561] Re: [Hyper-V] hv: util: move waiting for release to hv_utils_transport itself
** Also affects: linux (Ubuntu Zesty)
Importance: Undecided
Status: Confirmed
** Also affects: linux (Ubuntu Yakkety)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Xenial)
Status: New => In Progress
** Changed in: linux (Ubuntu Yakkety)
Status: New => In Progress
** Changed in: linux (Ubuntu Zesty)
Status: Confirmed => In Progress
** Changed in: linux (Ubuntu Xenial)
Importance: Undecided => Critical
** Changed in: linux (Ubuntu Yakkety)
Importance: Undecided => Critical
** Changed in: linux (Ubuntu Zesty)
Importance: Undecided => Critical
** Changed in: linux (Ubuntu Xenial)
Assignee: (unassigned) => Joseph Salisbury (jsalisbury)
** Changed in: linux (Ubuntu Yakkety)
Assignee: (unassigned) => Joseph Salisbury (jsalisbury)
** Changed in: linux (Ubuntu Zesty)
Assignee: (unassigned) => Joseph Salisbury (jsalisbury)
** Tags added: kernel-hyper-v xenial yakkety zesty
--
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/1682561
Title:
[Hyper-V] hv: util: move waiting for release to hv_utils_transport
itself
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Xenial:
In Progress
Status in linux source package in Yakkety:
In Progress
Status in linux source package in Zesty:
In Progress
Bug description:
We are observing call traces with the -73 and -74 proposed kernels
that look like this:
[ 240.408061] INFO: task kworker/14:1:179 blocked for more than 120 seconds.
[ 240.412299] Not tainted 4.4.0-73-generic #94-Ubuntu
[ 240.415546] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables
this message.
[ 240.420217] kworker/14:1D 8804e6f23b68 0 179 2
0x
[ 240.420229] Workqueue: hv_vmbus_con vmbus_onmessage_work [hv_vmbus]
[ 240.420236] 8804e6f23b68 000181f9 8804ed944600
8804e6fe3800
[ 240.420241] 8804e6f24000 c0187a48 c0187a40
8804e6fe3800
[ 240.420243] 8804ea196800 8804e6f23b80 81837845
7fff
[ 240.420245] Call Trace:
[ 240.420254] [] schedule+0x35/0x80
[ 240.420256] [] schedule_timeout+0x1b5/0x270
[ 240.420260] [] ? kfree+0x13a/0x150
[ 240.420264] [] ? kfree_const+0x22/0x30
[ 240.420268] [] ? kobject_release+0x94/0x190
[ 240.420270] [] ? kobject_put+0x27/0x50
[ 240.420272] [] wait_for_completion+0xb3/0x140
[ 240.420276] [] ? wake_up_q+0x70/0x70
[ 240.420284] [] hv_kvp_deinit+0x4f/0x60 [hv_utils]
[ 240.420288] [] util_remove+0x21/0x40 [hv_utils]
[ 240.420294] [] vmbus_remove+0x27/0x30 [hv_vmbus]
[ 240.420301] [] __device_release_driver+0xa1/0x150
[ 240.420303] [] device_release_driver+0x23/0x30
[ 240.420306] [] bus_remove_device+0x101/0x170
[ 240.420308] [] device_del+0x139/0x270
[ 240.420310] [] device_unregister+0x1e/0x60
[ 240.420313] [] vmbus_device_unregister+0x1f/0x50
[hv_vmbus]
[ 240.420316] [] vmbus_onoffer_rescind+0x91/0xb0
[hv_vmbus]
[ 240.420324] [] vmbus_onmessage+0x33/0xa0 [hv_vmbus]
[ 240.420327] [] vmbus_onmessage_work+0x21/0x30 [hv_vmbus]
[ 240.420331] [] process_one_work+0x165/0x480
[ 240.420335] [] worker_thread+0x4b/0x4c0
[ 240.420338] [] ? process_one_work+0x480/0x480
[ 240.420341] [] ? process_one_work+0x480/0x480
[ 240.420345] [] kthread+0xd8/0xf0
[ 240.420347] [] ? kthread_create_on_node+0x1e0/0x1e0
[ 240.420350] [] ret_from_fork+0x3f/0x70
[ 240.420352] [] ? kthread_create_on_node+0x1e0/0x1e0
[ 317.360035] serial8250: too much work for irq3
The following commit should fix this issue:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e9c18ae6eb2b312f16c63e34b43ea23926daa398
Waiting for release_event in all three drivers introduced issues on release
as on_reset() hook is not always called. E.g. if the device was never
opened we will never get the completion.
Move the waiting code to hvutil_transport_destroy() and make sure it is
only called when the device is open. hvt->lock serialization should
guarantee the absence of races.
Fixes: 5a66fecbf6aa ("Drivers: hv: util: kvp: Fix a rescind processing issue")
Fixes: 20951c7535b5 ("Drivers: hv: util: Fcopy: Fix a rescind processing
issue")
Fixes: d77044d142e9 ("Drivers: hv: util: Backup: Fix a rescind processing
issue")
Reported-by: Dexuan Cui
Tested-by: Dexuan Cui
Signed-off-by: Vitaly Kuznetsov
Signed-off-by: K. Y. Srinivasan
Signed-off-by: Greg Kroah-Hartman
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1682561/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe
[Kernel-packages] [Bug 1682561] Re: [Hyper-V] hv: util: move waiting for release to hv_utils_transport itself
Unfortunately this is another critical issue.
--
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/1682561
Title:
[Hyper-V] hv: util: move waiting for release to hv_utils_transport
itself
Status in linux package in Ubuntu:
Confirmed
Bug description:
We are observing call traces with the -73 and -74 proposed kernels
that look like this:
[ 240.408061] INFO: task kworker/14:1:179 blocked for more than 120 seconds.
[ 240.412299] Not tainted 4.4.0-73-generic #94-Ubuntu
[ 240.415546] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables
this message.
[ 240.420217] kworker/14:1D 8804e6f23b68 0 179 2
0x
[ 240.420229] Workqueue: hv_vmbus_con vmbus_onmessage_work [hv_vmbus]
[ 240.420236] 8804e6f23b68 000181f9 8804ed944600
8804e6fe3800
[ 240.420241] 8804e6f24000 c0187a48 c0187a40
8804e6fe3800
[ 240.420243] 8804ea196800 8804e6f23b80 81837845
7fff
[ 240.420245] Call Trace:
[ 240.420254] [] schedule+0x35/0x80
[ 240.420256] [] schedule_timeout+0x1b5/0x270
[ 240.420260] [] ? kfree+0x13a/0x150
[ 240.420264] [] ? kfree_const+0x22/0x30
[ 240.420268] [] ? kobject_release+0x94/0x190
[ 240.420270] [] ? kobject_put+0x27/0x50
[ 240.420272] [] wait_for_completion+0xb3/0x140
[ 240.420276] [] ? wake_up_q+0x70/0x70
[ 240.420284] [] hv_kvp_deinit+0x4f/0x60 [hv_utils]
[ 240.420288] [] util_remove+0x21/0x40 [hv_utils]
[ 240.420294] [] vmbus_remove+0x27/0x30 [hv_vmbus]
[ 240.420301] [] __device_release_driver+0xa1/0x150
[ 240.420303] [] device_release_driver+0x23/0x30
[ 240.420306] [] bus_remove_device+0x101/0x170
[ 240.420308] [] device_del+0x139/0x270
[ 240.420310] [] device_unregister+0x1e/0x60
[ 240.420313] [] vmbus_device_unregister+0x1f/0x50
[hv_vmbus]
[ 240.420316] [] vmbus_onoffer_rescind+0x91/0xb0
[hv_vmbus]
[ 240.420324] [] vmbus_onmessage+0x33/0xa0 [hv_vmbus]
[ 240.420327] [] vmbus_onmessage_work+0x21/0x30 [hv_vmbus]
[ 240.420331] [] process_one_work+0x165/0x480
[ 240.420335] [] worker_thread+0x4b/0x4c0
[ 240.420338] [] ? process_one_work+0x480/0x480
[ 240.420341] [] ? process_one_work+0x480/0x480
[ 240.420345] [] kthread+0xd8/0xf0
[ 240.420347] [] ? kthread_create_on_node+0x1e0/0x1e0
[ 240.420350] [] ret_from_fork+0x3f/0x70
[ 240.420352] [] ? kthread_create_on_node+0x1e0/0x1e0
[ 317.360035] serial8250: too much work for irq3
The following commit should fix this issue:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e9c18ae6eb2b312f16c63e34b43ea23926daa398
Waiting for release_event in all three drivers introduced issues on release
as on_reset() hook is not always called. E.g. if the device was never
opened we will never get the completion.
Move the waiting code to hvutil_transport_destroy() and make sure it is
only called when the device is open. hvt->lock serialization should
guarantee the absence of races.
Fixes: 5a66fecbf6aa ("Drivers: hv: util: kvp: Fix a rescind processing issue")
Fixes: 20951c7535b5 ("Drivers: hv: util: Fcopy: Fix a rescind processing
issue")
Fixes: d77044d142e9 ("Drivers: hv: util: Backup: Fix a rescind processing
issue")
Reported-by: Dexuan Cui
Tested-by: Dexuan Cui
Signed-off-by: Vitaly Kuznetsov
Signed-off-by: K. Y. Srinivasan
Signed-off-by: Greg Kroah-Hartman
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1682561/+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 1682561] Re: [Hyper-V] hv: util: move waiting for release to hv_utils_transport itself
This appears to affect 4.4, 4.8, and 4.10
--
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/1682561
Title:
[Hyper-V] hv: util: move waiting for release to hv_utils_transport
itself
Status in linux package in Ubuntu:
Confirmed
Bug description:
We are observing call traces with the -73 and -74 proposed kernels
that look like this:
[ 240.408061] INFO: task kworker/14:1:179 blocked for more than 120 seconds.
[ 240.412299] Not tainted 4.4.0-73-generic #94-Ubuntu
[ 240.415546] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables
this message.
[ 240.420217] kworker/14:1D 8804e6f23b68 0 179 2
0x
[ 240.420229] Workqueue: hv_vmbus_con vmbus_onmessage_work [hv_vmbus]
[ 240.420236] 8804e6f23b68 000181f9 8804ed944600
8804e6fe3800
[ 240.420241] 8804e6f24000 c0187a48 c0187a40
8804e6fe3800
[ 240.420243] 8804ea196800 8804e6f23b80 81837845
7fff
[ 240.420245] Call Trace:
[ 240.420254] [] schedule+0x35/0x80
[ 240.420256] [] schedule_timeout+0x1b5/0x270
[ 240.420260] [] ? kfree+0x13a/0x150
[ 240.420264] [] ? kfree_const+0x22/0x30
[ 240.420268] [] ? kobject_release+0x94/0x190
[ 240.420270] [] ? kobject_put+0x27/0x50
[ 240.420272] [] wait_for_completion+0xb3/0x140
[ 240.420276] [] ? wake_up_q+0x70/0x70
[ 240.420284] [] hv_kvp_deinit+0x4f/0x60 [hv_utils]
[ 240.420288] [] util_remove+0x21/0x40 [hv_utils]
[ 240.420294] [] vmbus_remove+0x27/0x30 [hv_vmbus]
[ 240.420301] [] __device_release_driver+0xa1/0x150
[ 240.420303] [] device_release_driver+0x23/0x30
[ 240.420306] [] bus_remove_device+0x101/0x170
[ 240.420308] [] device_del+0x139/0x270
[ 240.420310] [] device_unregister+0x1e/0x60
[ 240.420313] [] vmbus_device_unregister+0x1f/0x50
[hv_vmbus]
[ 240.420316] [] vmbus_onoffer_rescind+0x91/0xb0
[hv_vmbus]
[ 240.420324] [] vmbus_onmessage+0x33/0xa0 [hv_vmbus]
[ 240.420327] [] vmbus_onmessage_work+0x21/0x30 [hv_vmbus]
[ 240.420331] [] process_one_work+0x165/0x480
[ 240.420335] [] worker_thread+0x4b/0x4c0
[ 240.420338] [] ? process_one_work+0x480/0x480
[ 240.420341] [] ? process_one_work+0x480/0x480
[ 240.420345] [] kthread+0xd8/0xf0
[ 240.420347] [] ? kthread_create_on_node+0x1e0/0x1e0
[ 240.420350] [] ret_from_fork+0x3f/0x70
[ 240.420352] [] ? kthread_create_on_node+0x1e0/0x1e0
[ 317.360035] serial8250: too much work for irq3
The following commit should fix this issue:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e9c18ae6eb2b312f16c63e34b43ea23926daa398
Waiting for release_event in all three drivers introduced issues on release
as on_reset() hook is not always called. E.g. if the device was never
opened we will never get the completion.
Move the waiting code to hvutil_transport_destroy() and make sure it is
only called when the device is open. hvt->lock serialization should
guarantee the absence of races.
Fixes: 5a66fecbf6aa ("Drivers: hv: util: kvp: Fix a rescind processing issue")
Fixes: 20951c7535b5 ("Drivers: hv: util: Fcopy: Fix a rescind processing
issue")
Fixes: d77044d142e9 ("Drivers: hv: util: Backup: Fix a rescind processing
issue")
Reported-by: Dexuan Cui
Tested-by: Dexuan Cui
Signed-off-by: Vitaly Kuznetsov
Signed-off-by: K. Y. Srinivasan
Signed-off-by: Greg Kroah-Hartman
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1682561/+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
