From: Jani Nikula <jani.nikula@linux.intel.com>
To: Lucas De Marchi <lucas.demarchi@intel.com>,
intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 1/4] drm/i915/opregion: fix leaking fw on error path
Date: Fri, 08 Nov 2019 11:16:47 +0200 [thread overview]
Message-ID: <87mud6683k.fsf@intel.com> (raw)
In-Reply-To: <20191108003602.33526-1-lucas.demarchi@intel.com>
On Thu, 07 Nov 2019, Lucas De Marchi <lucas.demarchi@intel.com> wrote:
> Convert the code to return-early style and fix missing calls
> to release_firmware() if vbt is not valid.
I don't understand where anything would leak in the current code. Please
elaborate.
You could make a case for a change in style to avoid so much
indentation, but don't claim it fixes stuff if it doesn't.
>
> Signed-off-by: Lucas De Marchi <lucas.demarchi@intel.com>
> ---
> drivers/gpu/drm/i915/display/intel_opregion.c | 28 +++++++++++--------
> 1 file changed, 17 insertions(+), 11 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/display/intel_opregion.c b/drivers/gpu/drm/i915/display/intel_opregion.c
> index 969ade623691..9738511147b1 100644
> --- a/drivers/gpu/drm/i915/display/intel_opregion.c
> +++ b/drivers/gpu/drm/i915/display/intel_opregion.c
> @@ -872,23 +872,29 @@ static int intel_load_vbt_firmware(struct drm_i915_private *dev_priv)
> return ret;
> }
>
> - if (intel_bios_is_valid_vbt(fw->data, fw->size)) {
> - opregion->vbt_firmware = kmemdup(fw->data, fw->size, GFP_KERNEL);
> - if (opregion->vbt_firmware) {
> - DRM_DEBUG_KMS("Found valid VBT firmware \"%s\"\n", name);
> - opregion->vbt = opregion->vbt_firmware;
> - opregion->vbt_size = fw->size;
> - ret = 0;
> - } else {
> - ret = -ENOMEM;
> - }
> - } else {
> + if (!intel_bios_is_valid_vbt(fw->data, fw->size)) {
> DRM_DEBUG_KMS("Invalid VBT firmware \"%s\"\n", name);
> ret = -EINVAL;
> + goto err_release_fw;
> + }
> +
> + opregion->vbt_firmware = kmemdup(fw->data, fw->size, GFP_KERNEL);
> + if (!opregion->vbt_firmware) {
> + ret = -ENOMEM;
> + goto err_release_fw;
> }
>
> + opregion->vbt = opregion->vbt_firmware;
> + opregion->vbt_size = fw->size;
> +
> + DRM_DEBUG_KMS("Found valid VBT firmware \"%s\"\n", name);
> +
> release_firmware(fw);
>
> + return 0;
With ret = 0 at the beginning you could just remove the the above three
lines and let this run through the below code.
> +
> +err_release_fw:
> + release_firmware(fw);
Usually we'd have a blank line before the ret.
BR,
Jani.
> return ret;
> }
--
Jani Nikula, Intel Open Source Graphics Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
WARNING: multiple messages have this Message-ID (diff)
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Lucas De Marchi <lucas.demarchi@intel.com>,
intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH 1/4] drm/i915/opregion: fix leaking fw on error path
Date: Fri, 08 Nov 2019 11:16:47 +0200 [thread overview]
Message-ID: <87mud6683k.fsf@intel.com> (raw)
Message-ID: <20191108091647.4jeKvbBRkg7GHuYYedYseSYik2_wv7RyPfaudgMZ6wg@z> (raw)
In-Reply-To: <20191108003602.33526-1-lucas.demarchi@intel.com>
On Thu, 07 Nov 2019, Lucas De Marchi <lucas.demarchi@intel.com> wrote:
> Convert the code to return-early style and fix missing calls
> to release_firmware() if vbt is not valid.
I don't understand where anything would leak in the current code. Please
elaborate.
You could make a case for a change in style to avoid so much
indentation, but don't claim it fixes stuff if it doesn't.
>
> Signed-off-by: Lucas De Marchi <lucas.demarchi@intel.com>
> ---
> drivers/gpu/drm/i915/display/intel_opregion.c | 28 +++++++++++--------
> 1 file changed, 17 insertions(+), 11 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/display/intel_opregion.c b/drivers/gpu/drm/i915/display/intel_opregion.c
> index 969ade623691..9738511147b1 100644
> --- a/drivers/gpu/drm/i915/display/intel_opregion.c
> +++ b/drivers/gpu/drm/i915/display/intel_opregion.c
> @@ -872,23 +872,29 @@ static int intel_load_vbt_firmware(struct drm_i915_private *dev_priv)
> return ret;
> }
>
> - if (intel_bios_is_valid_vbt(fw->data, fw->size)) {
> - opregion->vbt_firmware = kmemdup(fw->data, fw->size, GFP_KERNEL);
> - if (opregion->vbt_firmware) {
> - DRM_DEBUG_KMS("Found valid VBT firmware \"%s\"\n", name);
> - opregion->vbt = opregion->vbt_firmware;
> - opregion->vbt_size = fw->size;
> - ret = 0;
> - } else {
> - ret = -ENOMEM;
> - }
> - } else {
> + if (!intel_bios_is_valid_vbt(fw->data, fw->size)) {
> DRM_DEBUG_KMS("Invalid VBT firmware \"%s\"\n", name);
> ret = -EINVAL;
> + goto err_release_fw;
> + }
> +
> + opregion->vbt_firmware = kmemdup(fw->data, fw->size, GFP_KERNEL);
> + if (!opregion->vbt_firmware) {
> + ret = -ENOMEM;
> + goto err_release_fw;
> }
>
> + opregion->vbt = opregion->vbt_firmware;
> + opregion->vbt_size = fw->size;
> +
> + DRM_DEBUG_KMS("Found valid VBT firmware \"%s\"\n", name);
> +
> release_firmware(fw);
>
> + return 0;
With ret = 0 at the beginning you could just remove the the above three
lines and let this run through the below code.
> +
> +err_release_fw:
> + release_firmware(fw);
Usually we'd have a blank line before the ret.
BR,
Jani.
> return ret;
> }
--
Jani Nikula, Intel Open Source Graphics Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2019-11-08 9:16 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-08 0:35 [PATCH 1/4] drm/i915/opregion: fix leaking fw on error path Lucas De Marchi
2019-11-08 0:35 ` [Intel-gfx] " Lucas De Marchi
2019-11-08 0:36 ` [PATCH 2/4] drm/i915/bios: rename bios to oprom when mapping pci rom Lucas De Marchi
2019-11-08 0:36 ` [Intel-gfx] " Lucas De Marchi
2019-11-08 10:01 ` Jani Nikula
2019-11-08 10:01 ` [Intel-gfx] " Jani Nikula
2019-11-08 0:36 ` [PATCH 3/4] drm/i915/bios: make sure to check vbt size Lucas De Marchi
2019-11-08 0:36 ` [Intel-gfx] " Lucas De Marchi
2019-11-08 10:08 ` Jani Nikula
2019-11-08 10:08 ` [Intel-gfx] " Jani Nikula
2019-11-08 17:41 ` Lucas De Marchi
2019-11-08 17:41 ` [Intel-gfx] " Lucas De Marchi
2019-11-08 0:36 ` [PATCH 4/4] drm/i915/bios: do not discard address space Lucas De Marchi
2019-11-08 0:36 ` [Intel-gfx] " Lucas De Marchi
2019-11-08 11:14 ` Jani Nikula
2019-11-08 11:14 ` [Intel-gfx] " Jani Nikula
2019-11-08 18:18 ` Lucas De Marchi
2019-11-08 18:18 ` [Intel-gfx] " Lucas De Marchi
2019-11-08 19:19 ` Ville Syrjälä
2019-11-08 19:19 ` [Intel-gfx] " Ville Syrjälä
2019-11-08 20:14 ` Lucas De Marchi
2019-11-08 20:14 ` [Intel-gfx] " Lucas De Marchi
2019-11-08 21:02 ` Ville Syrjälä
2019-11-08 21:02 ` [Intel-gfx] " Ville Syrjälä
2019-11-08 21:09 ` Lucas De Marchi
2019-11-08 21:09 ` [Intel-gfx] " Lucas De Marchi
2019-11-11 11:10 ` Jani Nikula
2019-11-11 11:10 ` [Intel-gfx] " Jani Nikula
2019-11-10 16:57 ` kbuild test robot
2019-11-10 16:57 ` [Intel-gfx] " kbuild test robot
2019-11-10 16:57 ` [RFC PATCH] drm/i915/bios: find_vbt() can be static kbuild test robot
2019-11-10 16:57 ` [Intel-gfx] " kbuild test robot
2019-11-08 1:53 ` ✗ Fi.CI.SPARSE: warning for series starting with [1/4] drm/i915/opregion: fix leaking fw on error path Patchwork
2019-11-08 1:53 ` [Intel-gfx] " Patchwork
2019-11-08 2:18 ` ✓ Fi.CI.BAT: success " Patchwork
2019-11-08 2:18 ` [Intel-gfx] " Patchwork
2019-11-08 9:16 ` Jani Nikula [this message]
2019-11-08 9:16 ` [Intel-gfx] [PATCH 1/4] " Jani Nikula
2019-11-08 17:34 ` Lucas De Marchi
2019-11-08 17:34 ` [Intel-gfx] " Lucas De Marchi
2019-11-09 13:23 ` ✓ Fi.CI.IGT: success for series starting with [1/4] " Patchwork
2019-11-09 13:23 ` [Intel-gfx] " 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=87mud6683k.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=lucas.demarchi@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