All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hans Verkuil <hverkuil+cisco@kernel.org>
To: Guangshuo Li <lgs201920130244@gmail.com>,
	Mauro Carvalho Chehab <mchehab@kernel.org>,
	Kees Cook <kees@kernel.org>, Wang Jun <1742789905@qq.com>,
	Steven Toth <stoth@kernellabs.com>,
	linux-media@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] media: saa7164: fix cleanup on resource allocation failure
Date: Wed, 15 Jul 2026 13:40:01 +0200	[thread overview]
Message-ID: <44181afe-0582-4a9e-9da0-05042da7f010@kernel.org> (raw)
In-Reply-To: <20260708072111.723453-1-lgs201920130244@gmail.com>

On 08/07/2026 09:21, Guangshuo Li wrote:
> saa7164_dev_setup() adds the device to the global saa7164_devlist before
> requesting the PCI BAR memory regions.
> 
> If get_resources() fails, saa7164_dev_setup() decrements the device count
> and returns an error, but leaves the device on saa7164_devlist. The probe
> error path then frees the device, leaving a dangling entry on the global
> list.
> 
> Remove the device from saa7164_devlist before returning from the
> get_resources() failure path, matching the cleanup done by the ioremap
> failure paths.
> 
> Also release BAR0 if BAR0 was successfully requested but the BAR2
> request fails.
> 
> Fixes: 443c1228d505 ("V4L/DVB (12923): SAA7164: Add support for the NXP SAA7164 silicon")
> Signed-off-by: Guangshuo Li <lgs201920130244@gmail.com>
> ---
>  drivers/media/pci/saa7164/saa7164-core.c | 6 ++++++
>  1 file changed, 6 insertions(+)
> 
> diff --git a/drivers/media/pci/saa7164/saa7164-core.c b/drivers/media/pci/saa7164/saa7164-core.c
> index 6bcde506adf5..225dbd3650da 100644
> --- a/drivers/media/pci/saa7164/saa7164-core.c
> +++ b/drivers/media/pci/saa7164/saa7164-core.c
> @@ -878,6 +878,9 @@ static int get_resources(struct saa7164_dev *dev)
>  		if (request_mem_region(pci_resource_start(dev->pci, 2),
>  			pci_resource_len(dev->pci, 2), dev->name))
>  			return 0;
> +
> +		release_mem_region(pci_resource_start(dev->pci, 0),
> +				   pci_resource_len(dev->pci, 0));
>  	}
>  
>  	printk(KERN_ERR "%s: can't get MMIO memory @ 0x%llx or 0x%llx\n",
> @@ -999,6 +1002,9 @@ static int saa7164_dev_setup(struct saa7164_dev *dev)
>  		printk(KERN_ERR "CORE %s No more PCIe resources for subsystem: %04x:%04x\n",
>  		       dev->name, dev->pci->subsystem_vendor,
>  		       dev->pci->subsystem_device);
> +		scoped_guard(mutex, &devlist) {
> +			list_del(&dev->devlist);
> +		}
>  
>  		saa7164_devcount--;

This should just be a goto into the error handling. You just need to add a new goto label
right after the 'release_resources' call.

>  		return -ENODEV;

This patch looks good otherwise.

Regards,

	Hans

      reply	other threads:[~2026-07-15 11:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-08  7:21 [PATCH] media: saa7164: fix cleanup on resource allocation failure Guangshuo Li
2026-07-15 11:40 ` Hans Verkuil [this message]

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=44181afe-0582-4a9e-9da0-05042da7f010@kernel.org \
    --to=hverkuil+cisco@kernel.org \
    --cc=1742789905@qq.com \
    --cc=kees@kernel.org \
    --cc=lgs201920130244@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@kernel.org \
    --cc=stoth@kernellabs.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.