From: Darren Hart <dvhart@infradead.org>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: linux-kernel@vger.kernel.org, platform-driver-x86@vger.kernel.org
Subject: Re: [PATCH v2 1/1] platform/x86: surface3-wmi: Balance locking on error path
Date: Thu, 15 Dec 2016 12:30:36 -0800 [thread overview]
Message-ID: <20161215203036.GC13207@f23x64.localdomain> (raw)
In-Reply-To: <20161215174106.13916-1-andriy.shevchenko@linux.intel.com>
On Thu, Dec 15, 2016 at 07:41:06PM +0200, Andy Shevchenko wrote:
> There is a possibility that lock will be left acquired.
> Consolidate error path under out_free_unlock label.
>
> Reported-by: kbuild test robot <fengguang.wu@intel.com>
> Reviewed-by: Benjamin Tissoires <benjamin.tissoires@redhat.com>
> Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> ---
> In v2:
> - address Darren's comments
> - update tags (in particular put proper email of reporter)
>
> I dare to push this to testing ahead. If anyone has objections, tell me asap.
Looks good, thanks.
Reviewed-by: Darren Hart <dvhart@linux.intel.com>
>
> drivers/platform/x86/surface3-wmi.c | 11 ++++++-----
> 1 file changed, 6 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/platform/x86/surface3-wmi.c b/drivers/platform/x86/surface3-wmi.c
> index 5553b2b85e0a..cbf4d83a7271 100644
> --- a/drivers/platform/x86/surface3-wmi.c
> +++ b/drivers/platform/x86/surface3-wmi.c
> @@ -60,10 +60,10 @@ static DEFINE_MUTEX(s3_wmi_lock);
>
> static int s3_wmi_query_block(const char *guid, int instance, int *ret)
> {
> + struct acpi_buffer output = { ACPI_ALLOCATE_BUFFER, NULL };
> acpi_status status;
> union acpi_object *obj;
> -
> - struct acpi_buffer output = { ACPI_ALLOCATE_BUFFER, NULL };
> + int error = 0;
>
> mutex_lock(&s3_wmi_lock);
> status = wmi_query_block(guid, instance, &output);
> @@ -77,13 +77,14 @@ static int s3_wmi_query_block(const char *guid, int instance, int *ret)
> obj->type == ACPI_TYPE_BUFFER ?
> obj->buffer.length : 0);
> }
> - kfree(obj);
> - return -EINVAL;
> + error = -EINVAL;
> + goto out_free_unlock;
> }
> *ret = obj->integer.value;
> + out_free_unlock:
> kfree(obj);
> mutex_unlock(&s3_wmi_lock);
> - return 0;
> + return error;
> }
>
> static inline int s3_wmi_query_lid(int *ret)
> --
> 2.11.0
>
> --
> To unsubscribe from this list: send the line "unsubscribe platform-driver-x86" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
--
Darren Hart
Intel Open Source Technology Center
prev parent reply other threads:[~2016-12-15 20:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-15 17:41 [PATCH v2 1/1] platform/x86: surface3-wmi: Balance locking on error path Andy Shevchenko
2016-12-15 20:30 ` Darren Hart [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=20161215203036.GC13207@f23x64.localdomain \
--to=dvhart@infradead.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=platform-driver-x86@vger.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