From: Dan Carpenter <dan.carpenter@oracle.com>
To: xkernel.wang@foxmail.com
Cc: jerome.pouiller@silabs.com, gregkh@linuxfoundation.org,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] staging: wfx: fix the error handling in wfx_init_common()
Date: Fri, 18 Feb 2022 14:34:22 +0300 [thread overview]
Message-ID: <20220218113422.GF2407@kadam> (raw)
In-Reply-To: <tencent_8F1C1B14CFE19C4A05FF632068CCCBB92708@qq.com>
On Thu, Feb 17, 2022 at 11:47:21PM +0800, xkernel.wang@foxmail.com wrote:
> diff --git a/drivers/staging/wfx/main.c b/drivers/staging/wfx/main.c
> index 4b9fdf9..f83df9f 100644
> --- a/drivers/staging/wfx/main.c
> +++ b/drivers/staging/wfx/main.c
> @@ -309,7 +309,8 @@ struct wfx_dev *wfx_init_common(struct device *dev,
> wdev->pdata.gpio_wakeup = devm_gpiod_get_optional(dev, "wakeup",
> GPIOD_OUT_LOW);
> if (IS_ERR(wdev->pdata.gpio_wakeup))
> - return NULL;
> + goto err;
> +
> if (wdev->pdata.gpio_wakeup)
> gpiod_set_consumer_name(wdev->pdata.gpio_wakeup, "wfx wakeup");
>
> @@ -325,9 +326,13 @@ struct wfx_dev *wfx_init_common(struct device *dev,
> wdev->force_ps_timeout = -1;
>
> if (devm_add_action_or_reset(dev, wfx_free_common, wdev))
> - return NULL;
> + goto err;
No, this goto introduces a double free. devm_add_action_or_reset()
will call wfx_free_common() on failure and then we call it again after
the goto.
regards,
dan carpenter
>
> return wdev;
> +
> +err:
> + ieee80211_free_hw(hw);
> + return NULL;
> }
Also the patchset was not sent as a thread.
regards,
dan carpenter
prev parent reply other threads:[~2022-02-18 11:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-17 15:47 [PATCH 1/2] staging: wfx: fix the error handling in wfx_init_common() xkernel.wang
2022-02-18 11:34 ` Dan Carpenter [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=20220218113422.GF2407@kadam \
--to=dan.carpenter@oracle.com \
--cc=gregkh@linuxfoundation.org \
--cc=jerome.pouiller@silabs.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=xkernel.wang@foxmail.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