From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
Cc: Navid Emamdoost <navid.emamdoost@gmail.com>,
emamd001@umn.edu, kjlu@umn.edu, smccaman@umn.edu,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jslaby@suse.com>, Vinod Koul <vkoul@kernel.org>,
linux-serial@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] 8250_lpss: check null return when calling pci_ioremap_bar
Date: Fri, 26 Jul 2019 14:57:46 +0300 [thread overview]
Message-ID: <20190726115746.GT9224@smile.fi.intel.com> (raw)
In-Reply-To: <afc360b9-6d05-72a6-4933-2fc0b84a7cf7@samsung.com>
On Fri, Jul 26, 2019 at 01:32:21PM +0200, Bartlomiej Zolnierkiewicz wrote:
> On 7/19/19 7:48 PM, Navid Emamdoost wrote:
> > pci_ioremap_bar may return null. This is eventually de-referenced at
> > drivers/dma/dw/core.c:1154 and drivers/dma/dw/core.c:1168. A null check
> > is needed to prevent null de-reference. I am adding the check and in case
> > of failure. Thanks to Andy Shevchenko for the hint on the necessity of
> > pci_iounmap when exiting.
> > @@ -169,10 +169,12 @@ static void qrk_serial_setup_dma(struct lpss8250 *lpss, struct uart_port *port)
> > struct pci_dev *pdev = to_pci_dev(port->dev);
> > int ret;
> >
> > + chip->pdata = &qrk_serial_dma_pdata;
> > chip->dev = &pdev->dev;
> > chip->irq = pci_irq_vector(pdev, 0);
> > chip->regs = pci_ioremap_bar(pdev, 1);
> > - chip->pdata = &qrk_serial_dma_pdata;
> > + if (!chip->regs)
> > + return;
> >
> > /* Falling back to PIO mode if DMA probing fails */
> > ret = dw_dma_probe(chip);
>
> pci_iounmap() should also be called on dw_dma_probe() failure (in such
> case param->dma_dev is NULL so pci_iounmap() in qrk_serial_exit_dma()
> won't be called during exit).
Oh, yes, good catch!
Navid, can you send a follow up fix?
> > @@ -195,11 +197,15 @@ static void qrk_serial_setup_dma(struct lpss8250 *lpss, struct uart_port *port)
> > pci_iounmap
> > static void qrk_serial_exit_dma(struct lpss8250 *lpss)
> > {
> > + struct dw_dma_chip *chip = &lpss->dma_chip;
> > struct dw_dma_slave *param = &lpss->dma_param;
> >
> > if (!param->dma_dev)
> > return;
> > - dw_dma_remove(&lpss->dma_chip);
> > +
> > + dw_dma_remove(chip);
> > +
> > + pci_iounmap(to_pci_dev(chip->dev), chip->regs);
> > }
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2019-07-26 11:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-19 2:54 [PATCH] 8250_lpss: check null return when calling pci_ioremap_bar Navid Emamdoost
2019-07-19 13:37 ` Andy Shevchenko
2019-07-19 15:15 ` Andy Shevchenko
2019-07-19 17:48 ` [PATCH v2] " Navid Emamdoost
2019-07-19 22:36 ` Andy Shevchenko
2019-07-26 11:32 ` Bartlomiej Zolnierkiewicz
2019-07-26 11:57 ` Andy Shevchenko [this message]
2019-07-26 19:53 ` [PATCH v3] " Navid Emamdoost
[not found] ` <CAEkB2ERhxLj7ogoy1E3j8d4MyEZqroWS1tPRxyJXR2oLhNz+LQ@mail.gmail.com>
2019-09-07 15:53 ` Andy Shevchenko
[not found] ` <CAEkB2ET-SQFiBbroxDFEVrPxto6a2wLJf0NM7R=ERcPargr66Q@mail.gmail.com>
2019-09-07 16:16 ` Andy Shevchenko
2019-07-19 13:58 ` [PATCH] " kbuild test robot
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=20190726115746.GT9224@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=b.zolnierkie@samsung.com \
--cc=emamd001@umn.edu \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.com \
--cc=kjlu@umn.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=navid.emamdoost@gmail.com \
--cc=smccaman@umn.edu \
--cc=vkoul@kernel.org \
/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