From: Ulf Hansson <ulf.hansson@linaro.org>
To: Yang Yingliang <yangyingliang@huawei.com>
Cc: linux-mmc@vger.kernel.org, linux-amlogic@lists.infradead.org,
neil.armstrong@linaro.org, khilman@baylibre.com,
jbrunet@baylibre.com, martin.blumenstingl@googlemail.com
Subject: Re: [PATCH] mmc: meson-gx: fix return value check of mmc_add_host()
Date: Wed, 9 Nov 2022 13:34:23 +0100 [thread overview]
Message-ID: <CAPDyKFq0RwWiH5uYqUZsjy89f89fMiFbcOhJ6L2V5zf6HYCR1Q@mail.gmail.com> (raw)
In-Reply-To: <20221108123417.479045-1-yangyingliang@huawei.com>
On Tue, 8 Nov 2022 at 13:35, Yang Yingliang <yangyingliang@huawei.com> wrote:
>
> mmc_add_host() may return error, if we ignore its return value,
> it will lead two issues:
> 1. The memory that allocated in mmc_alloc_host() is leaked.
> 2. In the remove() path, mmc_remove_host() will be called to
> delete device, but it's not added yet, it will lead a kernel
> crash because of null-ptr-deref in device_del().
>
> Fix this by checking the return value and goto error path which
> will call mmc_free_host().
>
> Fixes: 51c5d8447bd7 ("MMC: meson: initial support for GX platforms")
> Signed-off-by: Yang Yingliang <yangyingliang@huawei.com>
Applied for next, thanks!
Kind regards
Uffe
> ---
> drivers/mmc/host/meson-gx-mmc.c | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/mmc/host/meson-gx-mmc.c b/drivers/mmc/host/meson-gx-mmc.c
> index df05e60bed9a..6e5ea0213b47 100644
> --- a/drivers/mmc/host/meson-gx-mmc.c
> +++ b/drivers/mmc/host/meson-gx-mmc.c
> @@ -1335,7 +1335,9 @@ static int meson_mmc_probe(struct platform_device *pdev)
> }
>
> mmc->ops = &meson_mmc_ops;
> - mmc_add_host(mmc);
> + ret = mmc_add_host(mmc);
> + if (ret)
> + goto err_free_irq;
>
> return 0;
>
> --
> 2.25.1
>
prev parent reply other threads:[~2022-11-09 12:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-08 12:34 [PATCH] mmc: meson-gx: fix return value check of mmc_add_host() Yang Yingliang
2022-11-09 9:46 ` neil.armstrong
2022-11-09 12:34 ` Ulf Hansson [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=CAPDyKFq0RwWiH5uYqUZsjy89f89fMiFbcOhJ6L2V5zf6HYCR1Q@mail.gmail.com \
--to=ulf.hansson@linaro.org \
--cc=jbrunet@baylibre.com \
--cc=khilman@baylibre.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-mmc@vger.kernel.org \
--cc=martin.blumenstingl@googlemail.com \
--cc=neil.armstrong@linaro.org \
--cc=yangyingliang@huawei.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;
as well as URLs for NNTP newsgroup(s).