From: Kenji Kaneshige <kaneshige.kenji@jp.fujitsu.com>
To: Jiang Liu <liuj97@gmail.com>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
Yinghai Lu <yinghai@kernel.org>, Jiang Liu <jiang.liu@huawei.com>,
matsumoto.hiroo@jp.fujitsu.com,
Keping Chen <chenkeping@huawei.com>,
linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org
Subject: Re: [RFC PATCH 1/2] PCI: correctly flush workqueue when destroy pcie hotplug controller
Date: Tue, 10 Apr 2012 19:43:34 +0900 [thread overview]
Message-ID: <4F840ED6.3050408@jp.fujitsu.com> (raw)
In-Reply-To: <1333822735-10902-1-git-send-email-jiang.liu@huawei.com>
I think you're rignt.
Reviewed-by: Kenji Kaneshige <kaneshige.kenji@jp.fujitsu.com>
(2012/04/08 3:18), Jiang Liu wrote:
> When destroying a PCIe hotplug controller, all work items associated with
> that controller should be flushed. Function pcie_cleanup_slot() calls
> cancel_delayed_work() and flush_workqueue() to achieve that.
> Function flush_workqueue() will flush all work items already submitted,
> but new work items submitted by those already submitted work items may
> still be in live state when returning from flush_workqueue().
>
> For the extreme case, pciehp driver may expierence following calling path:
> 1) pcie_isr() -> pciehp_handle_xxx() -> queue_interrupt_event()->queue_work()
> 2) interrupt_event_handler() -> handle_button_press_event() ->
> queue_delayed_work()
> 3) pciehp_queue_pushbutton_work() -> queue_work()
>
> So enhance pcie_cleanup_slot() to correctly flush workqueue when destroying
> PCIe hotplug controller.
>
> Signed-off-by: Jiang Liu<jiang.liu@huawei.com>
> ---
> drivers/pci/hotplug/pciehp_hpc.c | 13 ++++++++++++-
> 1 files changed, 12 insertions(+), 1 deletions(-)
>
> diff --git a/drivers/pci/hotplug/pciehp_hpc.c b/drivers/pci/hotplug/pciehp_hpc.c
> index d4fa705..9a48a51 100644
> --- a/drivers/pci/hotplug/pciehp_hpc.c
> +++ b/drivers/pci/hotplug/pciehp_hpc.c
> @@ -890,8 +890,19 @@ static int pcie_init_slot(struct controller *ctrl)
> static void pcie_cleanup_slot(struct controller *ctrl)
> {
> struct slot *slot = ctrl->slot;
> - cancel_delayed_work(&slot->work);
> +
> + /*
> + * Following workqueue flushing logic is to deal with the special call path:
> + * 1) pcie_isr() -> pciehp_handle_xxx() ->
> + * queue_interrupt_event(pciehp_wq_event)->queue_work(pciehp_wq)
> + * 2) interrupt_event_handler() -> handle_button_press_event() ->
> + * queue_delayed_work(pciehp_wq)
> + * 3) pciehp_queue_pushbutton_work() -> queue_work(pciehp_wq)
> + */
> flush_workqueue(pciehp_wq);
> + cancel_delayed_work_sync(&slot->work);
> + flush_workqueue(pciehp_wq);
> +
> kfree(slot);
> }
>
next prev parent reply other threads:[~2012-04-10 10:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-07 18:18 [RFC PATCH 1/2] PCI: correctly flush workqueue when destroy pcie hotplug controller Jiang Liu
2012-04-07 18:18 ` [RFC PATCH 2/2] PCI: fix four race windows in shpchp driver Jiang Liu
2012-04-10 10:43 ` Kenji Kaneshige [this message]
2012-04-25 17:23 ` [RFC PATCH 1/2] PCI: correctly flush workqueue when destroy pcie hotplug controller Bjorn Helgaas
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=4F840ED6.3050408@jp.fujitsu.com \
--to=kaneshige.kenji@jp.fujitsu.com \
--cc=bhelgaas@google.com \
--cc=chenkeping@huawei.com \
--cc=jiang.liu@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=liuj97@gmail.com \
--cc=matsumoto.hiroo@jp.fujitsu.com \
--cc=yinghai@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.