From: Hans de Goede <hdegoede@redhat.com>
To: Chenyuan Yang <chenyuan0y@gmail.com>,
ilpo.jarvinen@linux.intel.com, rafael.j.wysocki@intel.com,
acelan.kao@canonical.com, u.kleine-koenig@baylibre.com
Cc: platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org, zijie98@gmail.com
Subject: Re: [PATCH v2] platform/x86: dell-uart-backlight: fix NULL pointer dereference in probe
Date: Mon, 13 Jan 2025 09:26:41 +0100 [thread overview]
Message-ID: <af6ef60f-d47f-4840-8466-4605ad59716f@redhat.com> (raw)
In-Reply-To: <20250111180118.2274516-1-chenyuan0y@gmail.com>
Hi,
On 11-Jan-25 7:01 PM, Chenyuan Yang wrote:
> The dell_uart_bl_serdev_probe() function calls devm_serdev_device_open()
> before setting the client ops via serdev_device_set_client_ops(). This
> ordering can trigger a NULL pointer dereference in the serdev controller's
> receive_buf handler, as it assumes serdev->ops is valid when
> SERPORT_ACTIVE is set.
>
> This is similar to the issue fixed in commit 5e700b384ec1
> ("platform/chrome: cros_ec_uart: properly fix race condition") where
> devm_serdev_device_open() was called before fully initializing the
> device.
>
> Fix the race by ensuring client ops are set before enabling the port via
> devm_serdev_device_open().
> Note, serdev_device_set_baudrate() and
> serdev_device_set_flow_control() calls should be
> after the devm_serdev_device_open() call.
>
> Fixes: 484bae9e4d6a ("platform/x86: Add new Dell UART backlight driver")
> Signed-off-by: Chenyuan Yang <chenyuan0y@gmail.com>
> CC: Hans de Goede <hdegoede@redhat.com>
Thanks, patch looks good to me:
Reviewed-by: Hans de Goede <hdegoede@redhat.com>
Regards,
Hans
> ---
> drivers/platform/x86/dell/dell-uart-backlight.c | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/platform/x86/dell/dell-uart-backlight.c b/drivers/platform/x86/dell/dell-uart-backlight.c
> index 6e5dc7e3674f..bcc5c0f3bb4d 100644
> --- a/drivers/platform/x86/dell/dell-uart-backlight.c
> +++ b/drivers/platform/x86/dell/dell-uart-backlight.c
> @@ -283,6 +283,9 @@ static int dell_uart_bl_serdev_probe(struct serdev_device *serdev)
> init_waitqueue_head(&dell_bl->wait_queue);
> dell_bl->dev = dev;
>
> + serdev_device_set_drvdata(serdev, dell_bl);
> + serdev_device_set_client_ops(serdev, &dell_uart_bl_serdev_ops);
> +
> ret = devm_serdev_device_open(dev, serdev);
> if (ret)
> return dev_err_probe(dev, ret, "opening UART device\n");
> @@ -290,8 +293,6 @@ static int dell_uart_bl_serdev_probe(struct serdev_device *serdev)
> /* 9600 bps, no flow control, these are the default but set them to be sure */
> serdev_device_set_baudrate(serdev, 9600);
> serdev_device_set_flow_control(serdev, false);
> - serdev_device_set_drvdata(serdev, dell_bl);
> - serdev_device_set_client_ops(serdev, &dell_uart_bl_serdev_ops);
>
> get_version[0] = DELL_SOF(GET_CMD_LEN);
> get_version[1] = CMD_GET_VERSION;
prev parent reply other threads:[~2025-01-13 8:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-11 18:01 Chenyuan Yang
2025-01-13 8:26 ` Hans de Goede [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=af6ef60f-d47f-4840-8466-4605ad59716f@redhat.com \
--to=hdegoede@redhat.com \
--cc=acelan.kao@canonical.com \
--cc=chenyuan0y@gmail.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=rafael.j.wysocki@intel.com \
--cc=u.kleine-koenig@baylibre.com \
--cc=zijie98@gmail.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
all inboxes | Powered by JetHome®