From: Manivannan Sadhasivam <mani@kernel.org>
To: Bo Liu <liubo03@inspur.com>
Cc: mani@kernel.org, quic_hemantk@quicinc.com, mhi@lists.linux.dev,
linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] bus: mhi: ep: Check dev_set_name() return value
Date: Sat, 9 Jul 2022 11:37:49 +0530 [thread overview]
Message-ID: <20220709060749.GB5063@thinkpad> (raw)
In-Reply-To: <20220708015948.4091-1-liubo03@inspur.com>
On Thu, Jul 07, 2022 at 09:59:48PM -0400, Bo Liu wrote:
> It's possible that dev_set_name() returns -ENOMEM, catch and handle this.
>
> Signed-off-by: Bo Liu <liubo03@inspur.com>
Reviewed-by: Manivannan Sadhasivam <mani@kernel.org>
Thanks,
Mani
> ---
> drivers/bus/mhi/ep/main.c | 11 +++++++++--
> 1 file changed, 9 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/bus/mhi/ep/main.c b/drivers/bus/mhi/ep/main.c
> index 40109a79017a..1dc8a3557a46 100644
> --- a/drivers/bus/mhi/ep/main.c
> +++ b/drivers/bus/mhi/ep/main.c
> @@ -1242,9 +1242,13 @@ static int mhi_ep_create_device(struct mhi_ep_cntrl *mhi_cntrl, u32 ch_id)
>
> /* Channel name is same for both UL and DL */
> mhi_dev->name = mhi_chan->name;
> - dev_set_name(&mhi_dev->dev, "%s_%s",
> + ret = dev_set_name(&mhi_dev->dev, "%s_%s",
> dev_name(&mhi_cntrl->mhi_dev->dev),
> mhi_dev->name);
> + if (ret) {
> + put_device(&mhi_dev->dev);
> + return ret;
> + }
>
> ret = device_add(&mhi_dev->dev);
> if (ret)
> @@ -1408,7 +1412,10 @@ int mhi_ep_register_controller(struct mhi_ep_cntrl *mhi_cntrl,
> goto err_free_irq;
> }
>
> - dev_set_name(&mhi_dev->dev, "mhi_ep%u", mhi_cntrl->index);
> + ret = dev_set_name(&mhi_dev->dev, "mhi_ep%u", mhi_cntrl->index);
> + if (ret)
> + goto err_put_dev;
> +
> mhi_dev->name = dev_name(&mhi_dev->dev);
> mhi_cntrl->mhi_dev = mhi_dev;
>
> --
> 2.27.0
>
--
மணிவண்ணன் சதாசிவம்
next prev parent reply other threads:[~2022-07-09 6:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-08 1:59 [PATCH] bus: mhi: ep: Check dev_set_name() return value Bo Liu
2022-07-09 6:07 ` Manivannan Sadhasivam [this message]
2022-07-09 6:11 ` Manivannan Sadhasivam
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=20220709060749.GB5063@thinkpad \
--to=mani@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liubo03@inspur.com \
--cc=mhi@lists.linux.dev \
--cc=quic_hemantk@quicinc.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