From: Huang Ying <ying.huang@intel.com>
To: Yijing Wang <wangyijing@huawei.com>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
Chen Gong <gong.chen@linux.intel.com>,
jiang.liu@huawei.com, Hanjun Guo <guohanjun@huawei.com>,
linux-pci@vger.kernel.org
Subject: Re: [PATCH v2 4/4] PCI/AER: fix a small race condition window when rmmod aer_inject
Date: Thu, 13 Sep 2012 09:29:21 +0800 [thread overview]
Message-ID: <1347499761.30040.138.camel@yhuang-dev> (raw)
In-Reply-To: <1347453225-7704-4-git-send-email-wangyijing@huawei.com>
On Wed, 2012-09-12 at 20:33 +0800, Yijing Wang wrote:
> Fix a small race condition window between pci_bus_ops_pop() and
> pci_bus_set_ops() functions.
>
> Signed-off-by: Yijing Wang <wangyijing@huawei.com>
> Signed-off-by: Jiang Liu <jiang.liu@huawei.com>
> ---
> drivers/pci/pcie/aer/aer_inject.c | 8 ++------
> 1 files changed, 2 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/pci/pcie/aer/aer_inject.c b/drivers/pci/pcie/aer/aer_inject.c
> index bd043db..69c2d77 100644
> --- a/drivers/pci/pcie/aer/aer_inject.c
> +++ b/drivers/pci/pcie/aer/aer_inject.c
> @@ -141,12 +141,11 @@ static struct pci_ops *__find_pci_bus_ops(struct pci_bus *bus)
> return NULL;
> }
>
> +/* inject_lock must be held before calling */
> static struct pci_bus_ops *pci_bus_ops_pop(void)
> {
> - unsigned long flags;
> struct pci_bus_ops *bus_ops = NULL;
>
> - spin_lock_irqsave(&inject_lock, flags);
> if (list_empty(&pci_bus_ops_list))
> bus_ops = NULL;
> else {
> @@ -154,7 +153,6 @@ static struct pci_bus_ops *pci_bus_ops_pop(void)
> list_del(lh);
> bus_ops = list_entry(lh, struct pci_bus_ops, list);
> }
> - spin_unlock_irqrestore(&inject_lock, flags);
> return bus_ops;
> }
>
> @@ -610,14 +608,12 @@ static void __exit aer_inject_exit(void)
> bus_unregister_notifier(&pci_bus_type, &aerinj_hp_notifier);
> misc_deregister(&aer_inject_device);
>
> + spin_lock_irqsave(&inject_lock, flags);
> while ((bus_ops = pci_bus_ops_pop())) {
> pci_bus_set_ops(bus_ops->bus, bus_ops->ops);
> kfree(bus_ops);
> }
>
> - clean_untracked_pci_aer_ops();
> -
> - spin_lock_irqsave(&inject_lock, flags);
> list_for_each_entry_safe(err, err_next, &einjected, list) {
> list_del(&err->list);
> kfree(err);
This may trigger a AB BA dead lock. In aer_inject_exit, the lock
sequence is:
inject_lock -> pci_lock
In pci config read/write path, the lock sequence is:
pci_lock -> inject_lock
With lockdep enabled, you may found warning on that.
Best Regards,
Huang YIng
next prev parent reply other threads:[~2012-09-13 1:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-12 12:33 [PATCH v2 1/4] PCI/AER: Fix pci_ops return NULL when hotplug a pci bus doing aer error inject Yijing Wang
2012-09-12 12:33 ` [PATCH v2 2/4] PCI/AER: clean all untracked pci_ops_aer when rmmod aer_inject Yijing Wang
2012-09-13 1:43 ` Huang Ying
2012-09-13 10:54 ` Yijing Wang
2012-09-14 0:56 ` Huang Ying
2012-09-14 1:29 ` Yijing Wang
2012-09-12 12:33 ` [PATCH v2 3/4] PCI/AER: Clean pci_bus_ops when related pci bus was removed Yijing Wang
2012-09-12 12:33 ` [PATCH v2 4/4] PCI/AER: fix a small race condition window when rmmod aer_inject Yijing Wang
2012-09-13 1:29 ` Huang Ying [this message]
2012-09-13 10:59 ` Yijing Wang
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=1347499761.30040.138.camel@yhuang-dev \
--to=ying.huang@intel.com \
--cc=bhelgaas@google.com \
--cc=gong.chen@linux.intel.com \
--cc=guohanjun@huawei.com \
--cc=jiang.liu@huawei.com \
--cc=linux-pci@vger.kernel.org \
--cc=wangyijing@huawei.com \
/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;
as well as URLs for NNTP newsgroup(s).