From: srinivas pandruvada <srinivas.pandruvada@linux.intel.com>
To: Dan Carpenter <error27@gmail.com>
Cc: Hans de Goede <hdegoede@redhat.com>,
Mark Gross <markgross@kernel.org>,
Zhang Rui <rui.zhang@intel.com>,
platform-driver-x86@vger.kernel.org,
kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] platform/x86: ISST: unlock on error path in tpmi_sst_init()
Date: Sat, 25 Mar 2023 12:31:48 -0700 [thread overview]
Message-ID: <b7368c892515483f6b041f970da30e99d225a554.camel@linux.intel.com> (raw)
In-Reply-To: <dcdebbb7-7de6-4d04-8e7a-43d5ca043484@kili.mountain>
This is for linux-next as this is not merged to mainline.
On Sat, 2023-03-25 at 14:08 +0300, Dan Carpenter wrote:
> Call mutex_unlock(&isst_tpmi_dev_lock) before returning on this
> error path.
>
> Fixes: d805456c712f ("platform/x86: ISST: Enumerate TPMI SST and
> create framework")
> Signed-off-by: Dan Carpenter <error27@gmail.com>
Acked-by: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
> ---
> drivers/platform/x86/intel/speed_select_if/isst_tpmi_core.c | 6
> ++++--
> 1 file changed, 4 insertions(+), 2 deletions(-)
>
> diff --git
> a/drivers/platform/x86/intel/speed_select_if/isst_tpmi_core.c
> b/drivers/platform/x86/intel/speed_select_if/isst_tpmi_core.c
> index cdb56a18ea17..664d2ee60385 100644
> --- a/drivers/platform/x86/intel/speed_select_if/isst_tpmi_core.c
> +++ b/drivers/platform/x86/intel/speed_select_if/isst_tpmi_core.c
> @@ -1399,8 +1399,10 @@ int tpmi_sst_init(void)
> isst_common.sst_inst = kcalloc(topology_max_packages(),
> sizeof(*isst_common.sst_inst),
> GFP_KERNEL);
> - if (!isst_common.sst_inst)
> - return -ENOMEM;
> + if (!isst_common.sst_inst) {
> + ret = -ENOMEM;
> + goto init_done;
> + }
>
> memset(&cb, 0, sizeof(cb));
> cb.cmd_size = sizeof(struct isst_if_io_reg);
next prev parent reply other threads:[~2023-03-25 19:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-25 11:08 [PATCH] platform/x86: ISST: unlock on error path in tpmi_sst_init() Dan Carpenter
2023-03-25 19:31 ` srinivas pandruvada [this message]
2023-03-27 13:19 ` Hans de Goede
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=b7368c892515483f6b041f970da30e99d225a554.camel@linux.intel.com \
--to=srinivas.pandruvada@linux.intel.com \
--cc=error27@gmail.com \
--cc=hdegoede@redhat.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=markgross@kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=rui.zhang@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