From: Jon Mason <jdmason@kudzu.us>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: Yang Yingliang <yangyingliang@huawei.com>,
linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org,
Frank.Li@nxp.com, kishon@ti.com, lpieralisi@kernel.org,
kw@linux.com, bhelgaas@google.com
Subject: Re: [PATCH -next v2] PCI: endpoint: pci-epf-vntb: fix error handle in epf_ntb_mw_bar_init()
Date: Fri, 12 Aug 2022 10:06:57 -0400 [thread overview]
Message-ID: <YvZegcACgf5vKTB1@kudzu.us> (raw)
In-Reply-To: <20220627202704.GA1775928@bhelgaas>
On Mon, Jun 27, 2022 at 03:27:04PM -0500, Bjorn Helgaas wrote:
> On Sat, Jun 25, 2022 at 10:15:16AM +0800, Yang Yingliang wrote:
> > In error case of epf_ntb_mw_bar_init(), memory window BARs should be
> > cleared, so add 'num_mws' parameter in epf_ntb_mw_bar_clear() and
> > calling it in error path to clear the BARs. Also add missing error
> > code when pci_epc_mem_alloc_addr() fails.
>
> Another one for Jon, since ff32fac00d97 appeared in -next via his
> tree
>
> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=ff32fac00d97
Sorry for the extremely long delay in response. This series is in my
ntb branch and will be in my pull request for v5.20 which should be
going out later today.
Thanks,
Jon
>
> > Fixes: ff32fac00d97 ("NTB: EPF: support NTB transfer between PCI RC and EP connection")
> > Reported-by: Hulk Robot <hulkci@huawei.com>
> > Signed-off-by: Yang Yingliang <yangyingliang@huawei.com>
> > ---
> > v2:
> > add error label err_set_bar and move pci_epc_clear_bar() to it
> > ---
> > drivers/pci/endpoint/functions/pci-epf-vntb.c | 20 ++++++++++++++-----
> > 1 file changed, 15 insertions(+), 5 deletions(-)
> >
> > diff --git a/drivers/pci/endpoint/functions/pci-epf-vntb.c b/drivers/pci/endpoint/functions/pci-epf-vntb.c
> > index ebf7e243eefa..ee9fee167d48 100644
> > --- a/drivers/pci/endpoint/functions/pci-epf-vntb.c
> > +++ b/drivers/pci/endpoint/functions/pci-epf-vntb.c
> > @@ -567,6 +567,8 @@ static int epf_ntb_db_bar_init(struct epf_ntb *ntb)
> > return -1;
> > }
> >
> > +static void epf_ntb_mw_bar_clear(struct epf_ntb *ntb, int num_mws);
> > +
> > /**
> > * epf_ntb_db_bar_clear() - Clear doorbell BAR and free memory
> > * allocated in peers outbound address space
> > @@ -625,13 +627,21 @@ static int epf_ntb_mw_bar_init(struct epf_ntb *ntb)
> > &ntb->vpci_mw_phy[i],
> > size);
> > if (!ntb->vpci_mw_addr[i]) {
> > + ret = -ENOMEM;
> > dev_err(dev, "Failed to allocate source address\n");
> > - goto err_alloc_mem;
> > + goto err_set_bar;
> > }
> > }
> >
> > return ret;
> > +
> > +err_set_bar:
> > + pci_epc_clear_bar(ntb->epf->epc,
> > + ntb->epf->func_no,
> > + ntb->epf->vfunc_no,
> > + &ntb->epf->bar[barno]);
> > err_alloc_mem:
> > + epf_ntb_mw_bar_clear(ntb, i);
> > return ret;
> > }
> >
> > @@ -640,12 +650,12 @@ static int epf_ntb_mw_bar_init(struct epf_ntb *ntb)
> > * @ntb: NTB device that facilitates communication between HOST and vHOST
> > *
> > */
> > -static void epf_ntb_mw_bar_clear(struct epf_ntb *ntb)
> > +static void epf_ntb_mw_bar_clear(struct epf_ntb *ntb, int num_mws)
> > {
> > enum pci_barno barno;
> > int i;
> >
> > - for (i = 0; i < ntb->num_mws; i++) {
> > + for (i = 0; i < num_mws; i++) {
> > barno = ntb->epf_ntb_bar[BAR_MW0 + i];
> > pci_epc_clear_bar(ntb->epf->epc,
> > ntb->epf->func_no,
> > @@ -774,7 +784,7 @@ static int epf_ntb_epc_init(struct epf_ntb *ntb)
> > return 0;
> >
> > err_write_header:
> > - epf_ntb_mw_bar_clear(ntb);
> > + epf_ntb_mw_bar_clear(ntb, ntb->num_mws);
> > err_mw_bar_init:
> > epf_ntb_db_bar_clear(ntb);
> > err_db_bar_init:
> > @@ -794,7 +804,7 @@ static int epf_ntb_epc_init(struct epf_ntb *ntb)
> > static void epf_ntb_epc_cleanup(struct epf_ntb *ntb)
> > {
> > epf_ntb_db_bar_clear(ntb);
> > - epf_ntb_mw_bar_clear(ntb);
> > + epf_ntb_mw_bar_clear(ntb, ntb->num_mws);
> > }
> >
> > #define EPF_NTB_R(_name) \
> > --
> > 2.25.1
> >
next prev parent reply other threads:[~2022-08-12 14:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-25 2:15 [PATCH -next v2] PCI: endpoint: pci-epf-vntb: fix error handle in epf_ntb_mw_bar_init() Yang Yingliang
2022-06-27 20:27 ` Bjorn Helgaas
2022-08-12 14:06 ` Jon Mason [this message]
2022-12-13 18:27 ` 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=YvZegcACgf5vKTB1@kudzu.us \
--to=jdmason@kudzu.us \
--cc=Frank.Li@nxp.com \
--cc=bhelgaas@google.com \
--cc=helgaas@kernel.org \
--cc=kishon@ti.com \
--cc=kw@linux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=yangyingliang@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