linux-media.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Evgeny Novikov <novikov@ispras.ru>
To: Akihiro Tsukada <tskd08@gmail.com>
Cc: Evgeny Novikov <novikov@ispras.ru>,
	Mauro Carvalho Chehab <mchehab@kernel.org>,
	Kirill Shilimanov <kirill.shilimanov@huawei.com>,
	linux-media@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH] media: pt3: Fix IO unmapping on error handling paths in probe
Date: Thu, 12 Aug 2021 12:24:35 +0300	[thread overview]
Message-ID: <20210812092435.8255-1-novikov@ispras.ru> (raw)

pt3_probe() did not free one of IO mappings in case when one of them was
successful while another one failed. The patch fixed that.

Found by Linux Driver Verification project (linuxtesting.org).

Signed-off-by: Evgeny Novikov <novikov@ispras.ru>
Co-developed-by: Kirill Shilimanov <kirill.shilimanov@huawei.com>
Signed-off-by: Kirill Shilimanov <kirill.shilimanov@huawei.com>
---
 drivers/media/pci/pt3/pt3.c | 20 +++++++++++++-------
 1 file changed, 13 insertions(+), 7 deletions(-)

diff --git a/drivers/media/pci/pt3/pt3.c b/drivers/media/pci/pt3/pt3.c
index c0bc86793355..f1bd2644435b 100644
--- a/drivers/media/pci/pt3/pt3.c
+++ b/drivers/media/pci/pt3/pt3.c
@@ -736,19 +736,24 @@ static int pt3_probe(struct pci_dev *pdev, const struct pci_device_id *ent)
 	pt3->pdev = pdev;
 	mutex_init(&pt3->lock);
 	pt3->regs[0] = pci_ioremap_bar(pdev, 0);
-	pt3->regs[1] = pci_ioremap_bar(pdev, 2);
-	if (pt3->regs[0] == NULL || pt3->regs[1] == NULL) {
+	if (pt3->regs[0] == NULL) {
 		dev_err(&pdev->dev, "Failed to ioremap\n");
 		ret = -ENOMEM;
 		goto err_kfree;
 	}
+	pt3->regs[1] = pci_ioremap_bar(pdev, 2);
+	if (pt3->regs[1] == NULL) {
+		dev_err(&pdev->dev, "Failed to ioremap\n");
+		ret = -ENOMEM;
+		goto err_iounmap0;
+	}
 
 	ver = ioread32(pt3->regs[0] + REG_VERSION);
 	if ((ver >> 16) != 0x0301) {
 		dev_warn(&pdev->dev, "PT%d, I/F-ver.:%d not supported\n",
 			 ver >> 24, (ver & 0x00ff0000) >> 16);
 		ret = -ENODEV;
-		goto err_iounmap;
+		goto err_iounmap1;
 	}
 
 	pt3->num_bufs = clamp_val(num_bufs, MIN_DATA_BUFS, MAX_DATA_BUFS);
@@ -756,7 +761,7 @@ static int pt3_probe(struct pci_dev *pdev, const struct pci_device_id *ent)
 	pt3->i2c_buf = kmalloc(sizeof(*pt3->i2c_buf), GFP_KERNEL);
 	if (pt3->i2c_buf == NULL) {
 		ret = -ENOMEM;
-		goto err_iounmap;
+		goto err_iounmap1;
 	}
 	i2c = &pt3->i2c_adap;
 	i2c->owner = THIS_MODULE;
@@ -801,11 +806,12 @@ static int pt3_probe(struct pci_dev *pdev, const struct pci_device_id *ent)
 	i2c_del_adapter(i2c);
 err_i2cbuf:
 	kfree(pt3->i2c_buf);
-err_iounmap:
-	if (pt3->regs[0])
-		pci_iounmap(pdev, pt3->regs[0]);
+err_iounmap1:
 	if (pt3->regs[1])
 		pci_iounmap(pdev, pt3->regs[1]);
+err_iounmap0:
+	if (pt3->regs[0])
+		pci_iounmap(pdev, pt3->regs[0]);
 err_kfree:
 	kfree(pt3);
 err_release_regions:
-- 
2.26.2


             reply	other threads:[~2021-08-12  9:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-12  9:24 Evgeny Novikov [this message]
     [not found] ` <CAHp75VcBnc_76E3KbmPPQKP5xfd73jAxz4Nx1WqCgPCnQN-Lsg@mail.gmail.com>
2021-08-14 15:44   ` [PATCH] media: pt3: Fix IO unmapping on error handling paths in probe Evgeny Novikov

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=20210812092435.8255-1-novikov@ispras.ru \
    --to=novikov@ispras.ru \
    --cc=kirill.shilimanov@huawei.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@kernel.org \
    --cc=tskd08@gmail.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).