From: Yijing Wang <wangyijing@huawei.com>
To: Huang Ying <ying.huang@intel.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 v4 2/5] PCI/AER: introduce pci_bus_ops_get() to avoid a small race condition window
Date: Fri, 21 Sep 2012 14:01:05 +0800 [thread overview]
Message-ID: <505C02A1.50601@huawei.com> (raw)
In-Reply-To: <1348204119.23395.21.camel@yhuang-dev>
On 2012/9/21 13:08, Huang Ying wrote:
> On Fri, 2012-09-21 at 11:44 +0800, Yijing Wang wrote:
>> When we rmmod aer_inject module, there is a small race condition window between pci_bus_ops_pop()
>> and pci_bus_set_ops() in aer_inject_exit, eg. pci_read_aer/pci_write_aer was called between
>> them. So introduce pci_bus_ops_get() to avoid this.
>>
>> Signed-off-by: Yijing Wang <wangyijing@huawei.com>
>> Signed-off-by: Huang Ying <ying.huang@intel.com>
>
> Please don't add my signed-off.
>
>> ---
>> drivers/pci/pcie/aer/aer_inject.c | 21 ++++++++++++++++++---
>> 1 files changed, 18 insertions(+), 3 deletions(-)
>>
>> diff --git a/drivers/pci/pcie/aer/aer_inject.c b/drivers/pci/pcie/aer/aer_inject.c
>> index fdab3bb..0123120 100644
>> --- a/drivers/pci/pcie/aer/aer_inject.c
>> +++ b/drivers/pci/pcie/aer/aer_inject.c
>> @@ -67,6 +67,8 @@ struct pci_bus_ops {
>> struct pci_ops *ops;
>> };
>>
>> +#define to_pci_bus_ops(n) container_of(n, struct pci_bus_ops, list)
>> +
>> static LIST_HEAD(einjected);
>>
>> static LIST_HEAD(pci_bus_ops_list);
>> @@ -160,6 +162,18 @@ static struct pci_bus_ops *pci_bus_ops_pop(void)
>> return bus_ops;
>> }
>>
>> +static struct pci_bus_ops *pci_bus_ops_get(struct pci_bus_ops *from)
>> +{
>> + struct pci_bus_ops *bus_ops = NULL;
>> + struct list_head *n;
>> +
>> + n = from ? from->list.next : pci_bus_ops_list.next;
>> + if (n != &pci_bus_ops_list)
>> + bus_ops = to_pci_bus_ops(n);
>> +
>> + return bus_ops;
>> +}
>> +
>> static u32 *find_pci_config_dword(struct aer_error *err, int where,
>> int *prw1cs)
>> {
>> @@ -539,14 +553,15 @@ static void __exit aer_inject_exit(void)
>> {
>> struct aer_error *err, *err_next;
>> unsigned long flags;
>> - struct pci_bus_ops *bus_ops;
>> + struct pci_bus_ops *bus_ops = NULL;
>>
>> misc_deregister(&aer_inject_device);
>>
>> - while ((bus_ops = pci_bus_ops_pop())) {
>> + while ((bus_ops = pci_bus_ops_get(bus_ops)))
>> pci_bus_set_ops(bus_ops->bus, bus_ops->ops);
>
> Why not just use
>
> list_for_each_entry(&pci_bus_ops_list) {
> pci_bus_set_ops();
> }
>
Yes, you are right, use list_for_each_entry(&pci_bus_ops_list) is cleaner.
Thanks
Yijing
> Best Regards,
> Huang Ying
>
>> +
>> + while ((bus_ops = pci_bus_ops_pop()))
>> kfree(bus_ops);
>> - }
>>
>> spin_lock_irqsave(&inject_lock, flags);
>> list_for_each_entry_safe(err, err_next, &einjected, list) {
>
>
>
> .
>
--
Thanks!
Yijing
next prev parent reply other threads:[~2012-09-21 6:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-21 3:44 [PATCH v4 0/5] Fix aer_inject bug caused by pci hot-plug Yijing Wang
2012-09-21 3:44 ` [PATCH v4 1/5] PCI/AER: Fix pci_ops return NULL in pci_read/write_aer Yijing Wang
2012-09-21 3:44 ` [PATCH v4 2/5] PCI/AER: introduce pci_bus_ops_get() to avoid a small race condition window Yijing Wang
2012-09-21 5:08 ` Huang Ying
2012-09-21 6:01 ` Yijing Wang [this message]
2012-09-21 3:44 ` [PATCH v4 3/5] PCI/AER: clean all untracked pci_ops_aer when rmmod aer_inject Yijing Wang
2012-09-21 5:13 ` Huang Ying
2012-09-21 5:47 ` Yijing Wang
2012-09-21 6:15 ` Huang Ying
2012-09-21 3:44 ` [PATCH v4 4/5] PCI/AER: clean pci_bus_ops when related pci bus was removed Yijing Wang
2012-09-21 3:44 ` [PATCH v4 5/5] PCI/AER: free pci_bus_ops_list and remove pci_bus_ops_pop Yijing Wang
2012-09-21 5:15 ` Huang Ying
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=505C02A1.50601@huawei.com \
--to=wangyijing@huawei.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=ying.huang@intel.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).