From: Johan Hovold <johan@kernel.org>
To: "Damien Riégel" <damien.riegel@silabs.com>
Cc: greybus-dev@lists.linaro.org, linux-staging@lists.linux.dev,
linux-kernel@vger.kernel.org, Alex Elder <elder@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Dan Carpenter <dan.carpenter@linaro.org>
Subject: Re: [PATCH v2 1/2] greybus: raw: fix use-after-free on cdev close
Date: Mon, 23 Mar 2026 15:22:52 +0100 [thread overview]
Message-ID: <acFMvCgcwIny-z2N@hovoldconsulting.com> (raw)
In-Reply-To: <20260319162049.42269-1-damien.riegel@silabs.com>
On Thu, Mar 19, 2026 at 12:20:48PM -0400, Damien Riégel wrote:
> This addresses a use-after-free bug when a raw bundle is disconnected
> but its chardev is still opened by an application. When the application
> releases the cdev, it causes the following panic when init on free is
> enabled (CONFIG_INIT_ON_FREE_DEFAULT_ON=y):
> Fixes: e806c7fb8e9b ("greybus: raw: add raw greybus kernel driver")
> Signed-off-by: Damien Riégel <damien.riegel@silabs.com>
> ---
> Changes in v2:
> - trim down trace in commit message to keep only the essential part
> - rework error paths in probe function to ensure device is always
> freed (set device release callback before any call to put_device)
> - move ida_free to release callback
> @@ -164,63 +172,58 @@ static int gb_raw_probe(struct gb_bundle *bundle,
> if (cport_desc->protocol_id != GREYBUS_PROTOCOL_RAW)
> return -ENODEV;
>
> + minor = ida_alloc(&minors, GFP_KERNEL);
> + if (minor < 0)
> + return minor;
> +
> raw = kzalloc(sizeof(*raw), GFP_KERNEL);
> - if (!raw)
> + if (!raw) {
> + ida_free(&minors, minor);
> return -ENOMEM;
> + }
> +
> + device_initialize(&raw->dev);
> + raw->dev.devt = MKDEV(raw_major, minor);
> + raw->dev.class = &raw_class;
> + raw->dev.release = raw_dev_release;
> + retval = dev_set_name(&raw->dev, "gb!raw%d", minor);
> + if (retval)
> + goto error_put_device;
>
> connection = gb_connection_create(bundle, le16_to_cpu(cport_desc->id),
> gb_raw_request_handler);
> if (IS_ERR(connection)) {
> retval = PTR_ERR(connection);
> - goto error_free;
> + goto error_put_device;
> }
>
> INIT_LIST_HEAD(&raw->list);
> mutex_init(&raw->list_lock);
>
> raw->connection = connection;
> + raw->dev.parent = &connection->bundle->dev;
You can set the parent above where you initialise dev since the probe
function is called with a pointer to the bundle (that is being bound).
> greybus_set_drvdata(bundle, raw);
Looks good otherwise:
Reviewed-by: Johan Hovold <johan@kernel.org>
Johan
prev parent reply other threads:[~2026-03-23 14:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-19 16:20 Damien Riégel
2026-03-19 16:20 ` [PATCH v2 2/2] greybus: raw: fix use-after-free if write is called after disconnect Damien Riégel
2026-03-23 14:30 ` Johan Hovold
2026-03-23 14:22 ` Johan Hovold [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=acFMvCgcwIny-z2N@hovoldconsulting.com \
--to=johan@kernel.org \
--cc=damien.riegel@silabs.com \
--cc=dan.carpenter@linaro.org \
--cc=elder@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=greybus-dev@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
/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
Powered by JetHome