From: Bjorn Helgaas <helgaas@kernel.org>
To: Dongdong Liu <liudongdong3@huawei.com>
Cc: wangzhou1@hisilicon.com, linux-pci@vger.kernel.org,
bhelgaas@google.com, gabriele.paoloni@huawei.com,
qiujiang@huawei.com, zhangjukuo@huawei.com,
haifeng.wei@huawei.com, yisen.zhuang@huawei.com
Subject: Re: [PATCH] PCI: hisi: fix the hisi_pcie_cfg_read bug when size=4
Date: Wed, 9 Dec 2015 10:16:43 -0600 [thread overview]
Message-ID: <20151209161643.GE31930@localhost> (raw)
In-Reply-To: <20151204224334.GL20125@localhost>
On Fri, Dec 04, 2015 at 04:43:34PM -0600, Bjorn Helgaas wrote:
> On Fri, Nov 27, 2015 at 12:58:00PM +0800, Dongdong Liu wrote:
> > Current hisi_pcie_cfg_read code read the RC configuration space,
> > this has a problem that the output parameter "*val" have not been
> > assigned when size=4, so we fix the bug by "*val = reg_val" when size=4.
> >
> > Signed-off-by: Dongdong Liu <liudongdong3@huawei.com>
>
> Wow, that's a pretty egregious bug. Was the hisi driver ever tested
> at all? We use dword reads in pci_bus_read_dev_vendor_id() to
> enumerate devices, so if those didn't return valid data, nothing at
> all should have worked.
>
> I tentatively put this on my for-linus branch for v4.4, but I wonder
> whether it might be smarter to revert the driver completely until I
> have more confidence in it.
>
> What sort of testing have you done on this driver?
Since I haven't heard anything about whether this driver was ever
tested, I dropped this patch from my for-linus branch and I reverted
the entire hisi driver.
Let me know when you have some testing results, and I'll take another
look at it.
Bjorn
> > ---
> > drivers/pci/host/pcie-hisi.c | 4 +++-
> > 1 file changed, 3 insertions(+), 1 deletion(-)
> >
> > diff --git a/drivers/pci/host/pcie-hisi.c b/drivers/pci/host/pcie-hisi.c
> > index 35457ec..da677b1 100644
> > --- a/drivers/pci/host/pcie-hisi.c
> > +++ b/drivers/pci/host/pcie-hisi.c
> > @@ -61,7 +61,9 @@ static int hisi_pcie_cfg_read(struct pcie_port *pp, int where, int size,
> > *val = *(u8 __force *) walker;
> > else if (size == 2)
> > *val = *(u16 __force *) walker;
> > - else if (size != 4)
> > + else if (size == 4)
> > + *val = reg_val;
> > + else
> > return PCIBIOS_BAD_REGISTER_NUMBER;
> >
> > return PCIBIOS_SUCCESSFUL;
> > --
> > 1.9.1
> >
> > --
> > To unsubscribe from this list: send the line "unsubscribe linux-pci" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at http://vger.kernel.org/majordomo-info.html
> --
> To unsubscribe from this list: send the line "unsubscribe linux-pci" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2015-12-09 16:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-27 4:58 [PATCH] PCI: hisi: fix the hisi_pcie_cfg_read bug when size=4 Dongdong Liu
2015-11-30 5:25 ` Zhou Wang
2015-12-04 22:43 ` Bjorn Helgaas
2015-12-09 16:16 ` Bjorn Helgaas [this message]
2015-12-09 20:36 ` Zhou Wang
2015-12-17 10:52 ` Zhou Wang
2015-12-17 18:43 ` 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=20151209161643.GE31930@localhost \
--to=helgaas@kernel.org \
--cc=bhelgaas@google.com \
--cc=gabriele.paoloni@huawei.com \
--cc=haifeng.wei@huawei.com \
--cc=linux-pci@vger.kernel.org \
--cc=liudongdong3@huawei.com \
--cc=qiujiang@huawei.com \
--cc=wangzhou1@hisilicon.com \
--cc=yisen.zhuang@huawei.com \
--cc=zhangjukuo@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 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.