public inbox for igt-dev@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Kamil Konieczny <kamil.konieczny@linux.intel.com>
To: igt-dev@lists.freedesktop.org
Cc: Badal Nilavar <badal.nilawar@intel.com>,
	Rodrigo Vivi <rodrigo.vivi@intel.com>
Subject: Re: [igt-dev] [PATCH i-g-t 1/3] lib/igt_pm: Refactor get firmware_node fd
Date: Mon, 7 Nov 2022 18:02:19 +0100	[thread overview]
Message-ID: <Y2k6G02oTAep271k@kamilkon-desk1> (raw)
In-Reply-To: <20221107131842.31387-2-anshuman.gupta@intel.com>

Hi Anshuman,

On 2022-11-07 at 18:48:40 +0530, Anshuman Gupta wrote:
> Created igt_pm_open_pci_firmware_node() to refactor
> the retrieving the firmware_node fd code.
> 
> igt_pm_open_pci_firmware_node() will be used by other
> firmware_node consumers.
> 
> While doing that fixed the leaked fd as well.
> 
> Signed-off-by: Anshuman Gupta <anshuman.gupta@intel.com>
> ---
>  lib/igt_pm.c | 29 ++++++++++++++++++++---------
>  1 file changed, 20 insertions(+), 9 deletions(-)
> 
> diff --git a/lib/igt_pm.c b/lib/igt_pm.c
> index 1e6e9ed3f..e289c48e4 100644
> --- a/lib/igt_pm.c
> +++ b/lib/igt_pm.c
> @@ -863,6 +863,20 @@ bool i915_output_is_lpsp_capable(int drm_fd, igt_output_t *output)
>  	return strstr(buf, "LPSP: capable");
>  }
>  
> +static int igt_pm_open_pci_firmware_node(struct pci_device *pci_dev)
> +{
> +	char name[PATH_MAX];
> +	int dir;
> +
> +	snprintf(name, PATH_MAX,
> +		 "/sys/bus/pci/devices/%04x:%02x:%02x.%01x/firmware_node",
> +		 pci_dev->domain, pci_dev->bus, pci_dev->dev, pci_dev->func);
> +
> +	dir = open(name, O_RDONLY);
> +
> +	return dir;
> +}
> +
>  /**
>   * igt_pm_acpi_d3cold_supported:
>   * @pci_dev: root port pci_dev.
> @@ -873,23 +887,20 @@ bool i915_output_is_lpsp_capable(int drm_fd, igt_output_t *output)
>   */
>  bool igt_pm_acpi_d3cold_supported(struct pci_device *pci_dev)
>  {
> -	char name[PATH_MAX];
> -	int dir, fd;
> +	int firmware_node_fd, fd;
>  
> -	snprintf(name, PATH_MAX,
> -		 "/sys/bus/pci/devices/%04x:%02x:%02x.%01x/firmware_node",
> -		 pci_dev->domain, pci_dev->bus, pci_dev->dev, pci_dev->func);
> -
> -	dir = open(name, O_RDONLY);
> -	igt_require(dir > 0);
> +	firmware_node_fd = igt_pm_open_pci_firmware_node(pci_dev);
> +	igt_require(firmware_node_fd > 0);

imho it is better just return false here.

>  
>  	/* BIOS need to enable ACPI D3Cold Support.*/
> -	fd = openat(dir, "real_power_state", O_RDONLY);
> +	fd = openat(firmware_node_fd, "real_power_state", O_RDONLY);
>  	if (fd < 0 && errno == ENOENT)

Here you should also close(firmware_node_fd) before return.
Btw check for errno looks strange.

>  		return false;
>  
>  	igt_require(fd > 0);

This is mixing two different error behaviour, return bool versus
igt_require, imho it is better to return false instead.

Regards,
Kamil

>  
> +	close(firmware_node_fd);
> +	close(fd);
>  	return true;
>  }
>  
> -- 
> 2.25.1
> 

  reply	other threads:[~2022-11-07 17:11 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-07 13:18 [igt-dev] [PATCH i-g-t 0/3] Cold Reset IGT Test Anshuman Gupta
2022-11-07 13:18 ` [igt-dev] [PATCH i-g-t 1/3] lib/igt_pm: Refactor get firmware_node fd Anshuman Gupta
2022-11-07 17:02   ` Kamil Konieczny [this message]
2022-11-08 11:48     ` Gupta, Anshuman
2022-11-07 13:18 ` [igt-dev] [PATCH i-g-t 2/3] test/device_reset: Refactor initiate_device_reset Anshuman Gupta
2022-11-07 21:32   ` Rodrigo Vivi
2022-11-14  7:54   ` Nilawar, Badal
2022-11-07 13:18 ` [igt-dev] [PATCH i-g-t 3/3] tests/device_reset: Add cold reset IGT test Anshuman Gupta
2022-11-14 11:59   ` Nilawar, Badal
2022-11-07 15:16 ` [igt-dev] ✓ Fi.CI.BAT: success for Cold Reset IGT Test Patchwork
2022-11-07 18:58 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork

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=Y2k6G02oTAep271k@kamilkon-desk1 \
    --to=kamil.konieczny@linux.intel.com \
    --cc=badal.nilawar@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=rodrigo.vivi@intel.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