From: Jiang Liu <jiang.liu@huawei.com>
To: Yijing Wang <wangyijing@huawei.com>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
Huang Ying <ying.huang@intel.com>,
Chen Gong <gong.chen@linux.intel.com>,
Hanjun Guo <guohanjun@huawei.com>, <linux-pci@vger.kernel.org>
Subject: Re: [PATCH 1/6] PCI/AER: fix pci_ops return NULL when hotplug a pci bus doing aer error inject
Date: Wed, 19 Sep 2012 16:19:12 +0800 [thread overview]
Message-ID: <50598000.1040501@huawei.com> (raw)
In-Reply-To: <1348022442-7816-2-git-send-email-wangyijing@huawei.com>
On 2012-9-19 10:40, Yijing Wang wrote:
> When we inject aer errors to the target pcie device by aer_inject module, the pci_ops of pci
> bus which the target device is on will be assigned to pci_ops_aer.So if the target pci device
> is a bridge, once we hot-remove and hot-add the bridge, the newly created child bus's pci_ops
> will be assigned to pci_ops_aer too.Now every access to the child bus's devices will result to
> system panic, because it get a NULL pci_ops in pci_read_aer/pci_write_aer.
>
> Signed-off-by: Yijing Wang <wangyijing@huawei.com>
> Signed-off-by: Jiang Liu <jiang.liu@huawei.com>
> Reviewed-by: Sven Dietrich <Sven.Dietrich@huawei.com>
> ---
> drivers/pci/pcie/aer/aer_inject.c | 27 ++++++++++++++++++++++++++-
> 1 files changed, 26 insertions(+), 1 deletions(-)
>
> diff --git a/drivers/pci/pcie/aer/aer_inject.c b/drivers/pci/pcie/aer/aer_inject.c
> index 4e24cb8..0f00a27 100644
> --- a/drivers/pci/pcie/aer/aer_inject.c
> +++ b/drivers/pci/pcie/aer/aer_inject.c
> @@ -109,6 +109,26 @@ static struct aer_error *__find_aer_error_by_dev(struct pci_dev *dev)
> return __find_aer_error((u16)domain, dev->bus->number, dev->devfn);
> }
>
> +/* find pci_ops of the nearest parent bus */
> +static struct pci_ops *__find_pci_bus_ops_parent(struct pci_bus *bus)
> +{
> + struct pci_bus_ops *bus_ops;
> + struct pci_bus *pbus = bus->parent;
> +
> + if (!pbus)
> + return NULL;
> +
> + while (pbus) {
> + list_for_each_entry(bus_ops, &pci_bus_ops_list, list)
> + if (bus_ops->bus == pbus)
> + return bus_ops->ops;
> +
> + pbus = pbus->parent;
> + }
> +
> + return NULL;
> +}
> +
> /* inject_lock must be held before calling */
> static struct pci_ops *__find_pci_bus_ops(struct pci_bus *bus)
> {
> @@ -118,7 +138,9 @@ static struct pci_ops *__find_pci_bus_ops(struct pci_bus *bus)
> if (bus_ops->bus == bus)
> return bus_ops->ops;
> }
> - return NULL;
> +
> + /* can't find bus_ops, fall back to get bus_ops of upstream bus */
> + return __find_pci_bus_ops_parent(bus);
> }
>
> static struct pci_bus_ops *pci_bus_ops_pop(void)
> @@ -208,6 +230,7 @@ static int pci_read_aer(struct pci_bus *bus, unsigned int devfn, int where,
> }
> out:
> ops = __find_pci_bus_ops(bus);
> + BUG_ON(!ops);
> spin_unlock_irqrestore(&inject_lock, flags);
> return ops->read(bus, devfn, where, size, val);
> }
> @@ -243,6 +266,7 @@ int pci_write_aer(struct pci_bus *bus, unsigned int devfn, int where, int size,
> }
> out:
> ops = __find_pci_bus_ops(bus);
> + BUG_ON(!ops);
How about move BUG_ON(!ops)into __find_pci_bus_ops?
> spin_unlock_irqrestore(&inject_lock, flags);
> return ops->write(bus, devfn, where, size, val);
> }
> @@ -506,6 +530,7 @@ static struct miscdevice aer_inject_device = {
> .fops = &aer_inject_fops,
> };
>
> +
Please remove this above line.
> static int __init aer_inject_init(void)
> {
> return misc_register(&aer_inject_device);
next prev parent reply other threads:[~2012-09-19 8:20 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-19 2:40 [PATCH 0/6] fix aer_inject bug while doing pci hot-plug Yijing Wang
2012-09-19 2:40 ` [PATCH 1/6] PCI/AER: fix pci_ops return NULL when hotplug a pci bus doing aer error inject Yijing Wang
2012-09-19 5:13 ` Huang Ying
2012-09-19 5:52 ` Yijing Wang
2012-09-19 8:19 ` Jiang Liu [this message]
2012-09-19 2:40 ` [PATCH 2/6] PCI/AER: introduce pci_bus_ops_get() function to avoid a small race condition window Yijing Wang
2012-09-19 5:52 ` Huang Ying
2012-09-19 6:42 ` Yijing Wang
2012-09-19 7:00 ` Huang Ying
2012-09-19 2:40 ` [PATCH 3/6] PCI/AER: clean all untracked pci_ops_aer when rmmod aer_inject Yijing Wang
2012-09-19 5:57 ` Huang Ying
2012-09-19 6:09 ` Yijing Wang
2012-09-19 6:18 ` Huang Ying
2012-09-19 6:36 ` Yijing Wang
2012-09-19 2:40 ` [PATCH 4/6] PCI/AER: clean pci_bus_ops when related pci bus was removed Yijing Wang
2012-09-19 2:40 ` [PATCH 5/6] PCI/AER: introduce pci_bus_ops_free to free pci_bus_ops Yijing Wang
2012-09-19 6:03 ` Huang Ying
2012-09-19 6:11 ` Yijing Wang
2012-09-19 7:11 ` Chen Gong
2012-09-19 7:29 ` Yijing Wang
2012-09-19 2:40 ` [PATCH 6/6] PCI/AER: clean unused code pci_bus_ops_pop Yijing Wang
2012-09-19 7:24 ` [PATCH 0/6] fix aer_inject bug while doing pci hot-plug Chen Gong
2012-09-19 7:32 ` 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=50598000.1040501@huawei.com \
--to=jiang.liu@huawei.com \
--cc=bhelgaas@google.com \
--cc=gong.chen@linux.intel.com \
--cc=guohanjun@huawei.com \
--cc=linux-pci@vger.kernel.org \
--cc=wangyijing@huawei.com \
--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 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.