From: Dawei Li <dawei.li@linux.dev>
To: Zhongqiu Han <zhongqiu.han@oss.qualcomm.com>
Cc: andersson@kernel.org, mathieu.poirier@linaro.org,
linux-remoteproc@vger.kernel.org, linux-kernel@vger.kernel.org,
set_pte_at@outlook.com, dawei.li@linux.dev
Subject: Re: [PATCH v4 1/3] rpmsg: char: Fix WARN() in error path of rpmsg_eptdev_add()
Date: Wed, 19 Nov 2025 18:56:12 +0800 [thread overview]
Message-ID: <20251119105612.GA4907@wendao-VirtualBox> (raw)
In-Reply-To: <38308885-af2e-4b61-9653-00bfca8ca0e9@oss.qualcomm.com>
On Wed, Nov 19, 2025 at 12:07:02PM +0800, Zhongqiu Han wrote:
> On 11/18/2025 11:41 PM, Dawei Li wrote:
> > put_device() is called on error path of rpmsg_eptdev_add() to cleanup
> > resource attached to eptdev->dev, unfortunately it's bogus cause
> > dev->release() is not set yet.
> >
> > When a struct device instance is destroyed, driver core framework checks
> > the possible release() callback from candidates below:
> > - struct device::release()
> > - dev->type->release()
> > - dev->class->dev_release()
> >
> > Rpmsg eptdev owns none of them so WARN() will complain the absence of
> > release().
> >
> > Fix it by:
> > - Pre-assign dev->release() before potential error path.
> > - Check before ida_free() in dev->release().
> >
> > By fixing error path of rpmsg_eptdev_add() and fixing potential memory
> > leak in rpmsg_anonymous_eptdev_create(), this work paves the way of rework
> > of rpmsg_eptdev_add() and its callers.
> >
> > Fixes: c0cdc19f84a4 ("rpmsg: Driver for user space endpoint interface")
> > Signed-off-by: Dawei Li <dawei.li@linux.dev>
> > ---
> > drivers/rpmsg/rpmsg_char.c | 26 +++++++++++++-------------
> > 1 file changed, 13 insertions(+), 13 deletions(-)
> >
> > diff --git a/drivers/rpmsg/rpmsg_char.c b/drivers/rpmsg/rpmsg_char.c
> > index 34b35ea74aab..373b627581e8 100644
> > --- a/drivers/rpmsg/rpmsg_char.c
> > +++ b/drivers/rpmsg/rpmsg_char.c
> > @@ -408,8 +408,13 @@ static void rpmsg_eptdev_release_device(struct device *dev)
> > {
> > struct rpmsg_eptdev *eptdev = dev_to_eptdev(dev);
> > - ida_free(&rpmsg_ept_ida, dev->id);
> > - if (eptdev->dev.devt)
> > + /*
> > + * release() can be invoked from error path of rpmsg_eptdev_add(),
> > + * WARN() will be fired if ida_free() is feed with invalid ID.
> > + */
> > + if (likely(ida_exists(&rpmsg_ept_ida, dev->id)))
> > + ida_free(&rpmsg_ept_ida, dev->id);
> > + if (eptdev->dev.devt && likely(ida_exists(&rpmsg_minor_ida, MINOR(eptdev->dev.devt))))
> > ida_free(&rpmsg_minor_ida, MINOR(eptdev->dev.devt));
> > kfree(eptdev);
> > }
> > @@ -458,6 +463,8 @@ static int rpmsg_eptdev_add(struct rpmsg_eptdev *eptdev,
> > struct device *dev = &eptdev->dev;
> > int ret;
> > + dev->release = rpmsg_eptdev_release_device;
> > +
> > eptdev->chinfo = chinfo;
> > if (cdev) {
> > @@ -471,7 +478,7 @@ static int rpmsg_eptdev_add(struct rpmsg_eptdev *eptdev,
> > /* Anonymous inode device still need device name for dev_err() and friends */
> > ret = ida_alloc(&rpmsg_ept_ida, GFP_KERNEL);
> > if (ret < 0)
> > - goto free_minor_ida;
> > + goto free_eptdev;
> > dev->id = ret;
> > dev_set_name(dev, "rpmsg%d", ret);
> > @@ -480,22 +487,13 @@ static int rpmsg_eptdev_add(struct rpmsg_eptdev *eptdev,
> > if (cdev) {
> > ret = cdev_device_add(&eptdev->cdev, &eptdev->dev);
> > if (ret)
> > - goto free_ept_ida;
> > + goto free_eptdev;
> > }
> > - /* We can now rely on the release function for cleanup */
> > - dev->release = rpmsg_eptdev_release_device;
> > -
> > return ret;
> > -free_ept_ida:
> > - ida_free(&rpmsg_ept_ida, dev->id);
> > -free_minor_ida:
> > - if (cdev)
> > - ida_free(&rpmsg_minor_ida, MINOR(dev->devt));
> > free_eptdev:
> > put_device(dev);
> > - kfree(eptdev);
>
>
> Hi Dawei,
>
> Thanks for your new version~
>
> Patch 1/3 will introduce a use-after-free of eptdev in func
> rpmsg_anonymous_eptdev_create(),
>
> https://git.kernel.org/pub/scm/linux/kernel/git/remoteproc/linux.git/tree/drivers/rpmsg/rpmsg_char.c?h=for-next#n548
>
> even though this issue will be resolved in 2/3. However, 1/3, as an
> independent commit, should not introduce a new bug.
FWIW, it's not new bug introduced by this commit, it's introduced by
2410558f5f11, which is supposed to be fixed in patch[2/3].
And new reorganize of series is trying to address the comments from
Mathieu[1], If I understand it correctly.
Bjorn, Mathieu,
What's your inputs on this? I will respin v5 if you find it necessary.
Diff between v5 from v4:
patch[1/3]: Remove dev_err(&eptdev->dev) from rpmsg_anonymous_eptdev_create();
patch[2/3]: Bring back dev_err(&eptdev->dev) to rpmsg_anonymous_eptdev_create();
[1] https://lore.kernel.org/all/aRd8mDzQWXtEFnmt@p14s/
>
>
> > return ret;
> > }
> > @@ -561,6 +559,8 @@ int rpmsg_anonymous_eptdev_create(struct rpmsg_device *rpdev, struct device *par
> > if (!ret)
> > *pfd = fd;
> > + else
> > + put_device(&eptdev->dev);
> > return ret;
> > }
>
>
> --
> Thx and BRs,
> Zhongqiu Han
Thanks,
Dawei
next prev parent reply other threads:[~2025-11-19 10:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-18 15:41 [PATCH v4 0/3] Fixes and rework of rpmsg_eptdev_add() Dawei Li
2025-11-18 15:41 ` [PATCH v4 1/3] rpmsg: char: Fix WARN() in error path " Dawei Li
2025-11-19 4:07 ` Zhongqiu Han
2025-11-19 10:56 ` Dawei Li [this message]
2025-11-19 12:26 ` Zhongqiu Han
2025-11-19 17:14 ` Mathieu Poirier
2025-11-18 15:41 ` [PATCH v4 2/3] rpmsg: char: Rework of rpmsg_eptdev_add() and its callers Dawei Li
2025-11-19 13:03 ` Zhongqiu Han
2025-11-18 15:41 ` [PATCH v4 3/3] rpmsg: char: Merge cdev branches in rpmsg_eptdev_add() Dawei Li
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=20251119105612.GA4907@wendao-VirtualBox \
--to=dawei.li@linux.dev \
--cc=andersson@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=set_pte_at@outlook.com \
--cc=zhongqiu.han@oss.qualcomm.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