From: Sasha Levin <sashal@kernel.org>
To: Dexuan Cui <decui@microsoft.com>
Cc: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
"lorenzo.pieralisi@arm.com" <lorenzo.pieralisi@arm.com>,
Michael Kelley <mikelley@microsoft.com>,
"stephen@networkplumber.org" <stephen@networkplumber.org>,
"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: FAILED: patch "[PATCH] PCI: hv: Add pci_destroy_slot() in" failed to apply to 4.14-stable tree
Date: Thu, 16 May 2019 20:48:54 -0400 [thread overview]
Message-ID: <20190517004854.GY11972@sasha-vm> (raw)
In-Reply-To: <PU1P153MB0169997D3F2274F83391D297BF090@PU1P153MB0169.APCP153.PROD.OUTLOOK.COM>
On Wed, May 15, 2019 at 11:20:45PM +0000, Dexuan Cui wrote:
>> From: gregkh@linuxfoundation.org <gregkh@linuxfoundation.org>
>> Sent: Wednesday, May 15, 2019 1:36 AM
>> To: Dexuan Cui <decui@microsoft.com>; lorenzo.pieralisi@arm.com; Michael
>> Kelley <mikelley@microsoft.com>; stephen@networkplumber.org
>> Cc: stable@vger.kernel.org
>> Subject: FAILED: patch "[PATCH] PCI: hv: Add pci_destroy_slot() in" failed to
>> apply to 4.14-stable tree
>>
>>
>> The patch below does not apply to the 4.14-stable tree.
>> If someone wants it applied there, or to any other stable or longterm
>> tree, then please email the backport, including the original git commit
>> id to <stable@vger.kernel.org>.
>>
>> thanks,
>>
>> greg k-h
>>
>> ------------------ original commit in Linus's tree ------------------
>>
>> From 340d455699400f2c2c0f9b3f703ade3085cdb501 Mon Sep 17 00:00:00
>> 2001
>> From: Dexuan Cui <decui@microsoft.com>
>> Date: Mon, 4 Mar 2019 21:34:49 +0000
>> Subject: [PATCH] PCI: hv: Add pci_destroy_slot() in
>> pci_devices_present_work(), if necessary
>>
>> When we hot-remove a device, usually the host sends us a PCI_EJECT message,
>> and a PCI_BUS_RELATIONS message with bus_rel->device_count == 0.
>>
>> When we execute the quick hot-add/hot-remove test, the host may not send
>> us the PCI_EJECT message if the guest has not fully finished the
>> initialization by sending the PCI_RESOURCES_ASSIGNED* message to the
>> host, so it's potentially unsafe to only depend on the
>> pci_destroy_slot() in hv_eject_device_work() because the code path
>>
>> create_root_hv_pci_bus()
>> -> hv_pci_assign_slots()
>>
>> is not called in this case. Note: in this case, the host still sends the
>> guest a PCI_BUS_RELATIONS message with bus_rel->device_count == 0.
>>
>> In the quick hot-add/hot-remove test, we can have such a race before
>> the code path
>>
>> pci_devices_present_work()
>> -> new_pcichild_device()
>>
>> adds the new device into the hbus->children list, we may have already
>> received the PCI_EJECT message, and since the tasklet handler
>>
>> hv_pci_onchannelcallback()
>>
>> may fail to find the "hpdev" by calling
>>
>> get_pcichild_wslot(hbus, dev_message->wslot.slot)
>>
>> hv_pci_eject_device() is not called; Later, by continuing execution
>>
>> create_root_hv_pci_bus()
>> -> hv_pci_assign_slots()
>>
>> creates the slot and the PCI_BUS_RELATIONS message with
>> bus_rel->device_count == 0 removes the device from hbus->children, and
>> we end up being unable to remove the slot in
>>
>> hv_pci_remove()
>> -> hv_pci_remove_slots()
>>
>> Remove the slot in pci_devices_present_work() when the device
>> is removed to address this race.
>>
>> pci_devices_present_work() and hv_eject_device_work() run in the
>> singled-threaded hbus->wq, so there is not a double-remove issue for the
>> slot.
>>
>> We cannot offload hv_pci_eject_device() from hv_pci_onchannelcallback()
>> to the workqueue, because we need the hv_pci_onchannelcallback()
>> synchronously call hv_pci_eject_device() to poll the channel
>> ringbuffer to work around the "hangs in hv_compose_msi_msg()" issue
>> fixed in commit de0aa7b2f97d ("PCI: hv: Fix 2 hang issues in
>> hv_compose_msi_msg()")
>>
>> Fixes: a15f2c08c708 ("PCI: hv: support reporting serial number as slot
>> information")
>> Signed-off-by: Dexuan Cui <decui@microsoft.com>
>> [lorenzo.pieralisi@arm.com: rewritten commit log]
>> Signed-off-by: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
>> Reviewed-by: Stephen Hemminger <stephen@networkplumber.org>
>> Reviewed-by: Michael Kelley <mikelley@microsoft.com>
>> Cc: stable@vger.kernel.org
>>
>> diff --git a/drivers/pci/controller/pci-hyperv.c
>> b/drivers/pci/controller/pci-hyperv.c
>> index b489412e3502..82acd6155adf 100644
>> --- a/drivers/pci/controller/pci-hyperv.c
>> +++ b/drivers/pci/controller/pci-hyperv.c
>> @@ -1776,6 +1776,10 @@ static void pci_devices_present_work(struct
>> work_struct *work)
>> hpdev = list_first_entry(&removed, struct hv_pci_dev,
>> list_entry);
>> list_del(&hpdev->list_entry);
>> +
>> + if (hpdev->pci_slot)
>> + pci_destroy_slot(hpdev->pci_slot);
>> +
>> put_pcichild(hpdev);
>> }
>>
>
>Hi,
>I backported the patch for linux-4.14.y.
>
>Please use the attached patch, which is [PATCH 3/3]
>
>Thanks,
>-- Dexuan
Queued for 4.14, thank you.
--
Thanks,
Sasha
prev parent reply other threads:[~2019-05-17 0:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-15 8:35 FAILED: patch "[PATCH] PCI: hv: Add pci_destroy_slot() in" failed to apply to 4.14-stable tree gregkh
2019-05-15 23:20 ` Dexuan Cui
2019-05-17 0:48 ` Sasha Levin [this message]
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=20190517004854.GY11972@sasha-vm \
--to=sashal@kernel.org \
--cc=decui@microsoft.com \
--cc=gregkh@linuxfoundation.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=mikelley@microsoft.com \
--cc=stable@vger.kernel.org \
--cc=stephen@networkplumber.org \
/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