From: Vitaly Kuznetsov <vkuznets@redhat.com>
To: "K. Y. Srinivasan" <kys@microsoft.com>, devel@linuxdriverproject.org
Cc: Thomas Gleixner <tglx@linutronix.de>,
Haiyang Zhang <haiyangz@microsoft.com>,
linux-kernel@vger.kernel.org, Dexuan Cui <decui@microsoft.com>
Subject: [PATCH v2 0/5] Drivers: hv: vmbus: fix crashes on hv_vmbus load/unload path
Date: Tue, 27 Jan 2015 17:44:14 +0100 [thread overview]
Message-ID: <1422377059-7858-1-git-send-email-vkuznets@redhat.com> (raw)
Changes since v1:
- '[PATCH 2/3] Drivers: hv: vmbus: introduce vmbus_acpi_remove' was dropped in
favor of Jake's '[PATCH v2 1/1] drivers:hv:vmbus drivers:hv:vmbus Allow for
more than one MMIO range for children'. It is required to make unload/load
work on Gen2 instances.
- Added '[PATCH v2 3/5] drivers: hv: Teardown synthetic interrupt controllers
on module unload' to deal with synic.
- Added '[PATCH v2 4/5] clockevents: export clockevents_unbind_device instead
of clockevents_unbind'. It is not for Hyper-V subsystem, however, it is a
pre-requisite for 'PATCH 5/5' and a natural part of this series. CC: Thomas
Gleixner as the subsystem maintainer.
- Added '[PATCH v2 5/5] Drivers: hv: vmbus: Teardown clockevent devices on
module unload' to deal with clockevent devices.
Patches are supposed to be applied on top of current char-misc-next tree.
Original description:
It is possible (since 93e5bd06a953: "Drivers: hv: Make the vmbus driver
unloadable") to unload hv_vmbus driver if no other devices are connected.
1aec169673d7: "x86: Hyperv: Cleanup the irq mess" fixed doulble interrupt
gate setup. However, if we try to unload hv_vmbus and then load it back
crashes in different places of vmbus driver occur on both unload and second
load paths. Address those I saw in my testing.
Not everything is fixed though. MCE was hit once on Generation2 instance and
I neither understand what caused it nor do I know the way to reproduce it.
Anyway, here is the log:
[ 204.846255] mce: [Hardware Error]: CPU 0: Machine Check Exception: 4 Bank 0: b2000000c0020001
[ 204.846675] mce: [Hardware Error]: TSC 6b5cd64bc8
[ 204.846675] mce: [Hardware Error]: PROCESSOR 0:306e4 TIME 1421944123 SOCKET 0 APIC 0 microcode ffffffff
[ 204.846675] mce: [Hardware Error]: Run the above through 'mcelog --ascii'
[ 204.846675] mce: [Hardware Error]: Machine check: Processor context corrupt
[ 204.846675] Kernel panic - not syncing: Fatal Machine check
[ 204.846675] Kernel Offset: 0x0 from 0xffffffff81000000 (relocation range: 0xffffffff80000000-0xffffffff9fffffff)
[ 204.846675] Rebooting in 30 seconds..
[ 204.846675] ACPI MEMORY or I/O RESET_REG.
Vitaly Kuznetsov (5):
Drivers: hv: vmbus: avoid double kfree for device_obj
Drivers: hv: vmbus: teardown hv_vmbus_con workqueue and
vmbus_connection pages on shutdown
drivers: hv: Teardown synthetic interrupt controllers on module unload
clockevents: export clockevents_unbind_device instead of
clockevents_unbind
Drivers: hv: vmbus: Teardown clockevent devices on module unload
drivers/hv/channel_mgmt.c | 1 -
drivers/hv/connection.c | 17 ++++++++++++-----
drivers/hv/hv.c | 34 +++++++++++++++++++++++++++++++---
drivers/hv/hyperv_vmbus.h | 3 +++
drivers/hv/vmbus_drv.c | 11 +++++++++++
kernel/time/clockevents.c | 2 +-
6 files changed, 58 insertions(+), 10 deletions(-)
--
1.9.3
next reply other threads:[~2015-01-27 16:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-27 16:44 Vitaly Kuznetsov [this message]
2015-01-27 16:44 ` [PATCH v2 1/5] Drivers: hv: vmbus: avoid double kfree for device_obj Vitaly Kuznetsov
2015-01-27 16:44 ` [PATCH v2 2/5] Drivers: hv: vmbus: teardown hv_vmbus_con workqueue and vmbus_connection pages on shutdown Vitaly Kuznetsov
2015-01-27 16:44 ` [PATCH v2 3/5] drivers: hv: Teardown synthetic interrupt controllers on module unload Vitaly Kuznetsov
2015-01-27 16:44 ` [PATCH v2 4/5] clockevents: export clockevents_unbind_device instead of clockevents_unbind Vitaly Kuznetsov
2015-01-27 16:44 ` [PATCH v2 5/5] Drivers: hv: vmbus: Teardown clockevent devices on module unload Vitaly Kuznetsov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1422377059-7858-1-git-send-email-vkuznets@redhat.com \
--to=vkuznets@redhat.com \
--cc=decui@microsoft.com \
--cc=devel@linuxdriverproject.org \
--cc=haiyangz@microsoft.com \
--cc=kys@microsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®