From: sashiko-bot@kernel.org
To: "Mallesh Koujalagi" <mallesh.koujalagi@intel.com>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [PATCH v10 3/4] drm/doc: Document DRM_WEDGE_RECOVERY_COLD_RESET recovery method
Date: Mon, 13 Jul 2026 08:47:42 +0000 [thread overview]
Message-ID: <20260713084743.4DBCA1F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260713083939.251872-9-mallesh.koujalagi@intel.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] Missing udev rule line continuation causes the example recovery script to execute for every system uevent.
--
--- Patch [3]: [PATCH v10 3/4] drm/doc: Document DRM_WEDGE_RECOVERY_COLD_RESET recovery method ---
commit 38af50f95ad4b618e8f2b464d3185bfdd320b4f3
Author: Mallesh Koujalagi <mallesh.koujalagi@intel.com>
drm/doc: Document DRM_WEDGE_RECOVERY_COLD_RESET recovery method
This commit documents the cold-reset recovery method for devices that encounter
unrecoverable errors. It provides an example udev rule and shell script to
handle cutting and restoring power to the PCIe slot.
> diff --git a/Documentation/gpu/drm-uapi.rst b/Documentation/gpu/drm-uapi.rst
> index 93df92c4ac8cf..43294a10738e6 100644
> --- a/Documentation/gpu/drm-uapi.rst
> +++ b/Documentation/gpu/drm-uapi.rst
[ ... ]
> @@ -530,6 +542,77 @@ Recovery script::
> echo -n $DEVICE > $DRIVER/unbind
> echo -n $DEVICE > $DRIVER/bind
>
> +Example - cold-reset
> +--------------------
> +
> +Udev rule::
> +
> + SUBSYSTEM=="drm", ENV{WEDGED}=="cold-reset", DEVPATH=="*/drm/card[0-9]",
> + RUN+="/path/to/cold-reset.sh $env{DEVPATH}"
[Severity: Medium]
Since udev rules are line-based, does missing a line continuation character
(\) here cause the second line to be parsed as a standalone, unconditional
rule?
If an administrator copies this example verbatim, it appears that
cold-reset.sh might be executed for every single system uevent. While the
script exits early for non-PCI devices, spawning a shell script for every
uevent (add, remove, change, etc.) could cause severe system performance
degradation and boot delays.
> +
> +Recovery script::
> +
> + #!/bin/sh
> + die() { echo "ERROR: $*" >&2; exit 1; }
[ ... ]
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260713083939.251872-6-mallesh.koujalagi@intel.com?part=3
next prev parent reply other threads:[~2026-07-13 8:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-13 8:39 [PATCH v10 0/4] Introduce cold reset recovery method Mallesh Koujalagi
2026-07-13 8:39 ` [PATCH v10 1/4] drm/xe/xe_ras: Do not Review, compilation only Mallesh Koujalagi
2026-07-13 8:54 ` sashiko-bot
2026-07-13 8:39 ` [PATCH v10 2/4] drm: Add DRM_WEDGE_RECOVERY_COLD_RESET recovery method Mallesh Koujalagi
2026-07-13 8:53 ` sashiko-bot
2026-07-13 8:39 ` [PATCH v10 3/4] drm/doc: Document " Mallesh Koujalagi
2026-07-13 8:47 ` sashiko-bot [this message]
2026-07-13 8:39 ` [PATCH v10 4/4] drm/xe: Handle PUNIT errors by requesting cold-reset recovery Mallesh Koujalagi
2026-07-13 8:54 ` sashiko-bot
2026-07-13 9:14 ` ✓ CI.KUnit: success for Introduce cold reset recovery method (rev10) Patchwork
2026-07-13 9:58 ` ✓ Xe.CI.BAT: " Patchwork
2026-07-13 11:54 ` ✓ Xe.CI.FULL: " Patchwork
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=20260713084743.4DBCA1F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=mallesh.koujalagi@intel.com \
--cc=sashiko-reviews@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.