lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250511224745.834446-3-andrealmeid@igalia.com>
Date: Sun, 11 May 2025 19:47:44 -0300
From: André Almeida <andrealmeid@...lia.com>
To: "Alex Deucher" <alexander.deucher@....com>,
	Christian König <christian.koenig@....com>,
	siqueira@...lia.com,
	airlied@...il.com,
	simona@...ll.ch,
	"Raag Jadav" <raag.jadav@...el.com>,
	rodrigo.vivi@...el.com,
	jani.nikula@...ux.intel.com,
	Xaver Hugl <xaver.hugl@...il.com>,
	"Pierre-Loup A . Griffais" <pgriffais@...vesoftware.com>
Cc: dri-devel@...ts.freedesktop.org,
	linux-kernel@...r.kernel.org,
	kernel-dev@...lia.com,
	amd-gfx@...ts.freedesktop.org,
	intel-xe@...ts.freedesktop.org,
	intel-gfx@...ts.freedesktop.org,
	André Almeida <andrealmeid@...lia.com>
Subject: [PATCH v2 2/3] drm/doc: Add a section about "App information" for the wedge API

Add a section about "App information" for the wedge API.

Signed-off-by: André Almeida <andrealmeid@...lia.com>
---
 Documentation/gpu/drm-uapi.rst | 15 +++++++++++++++
 1 file changed, 15 insertions(+)

diff --git a/Documentation/gpu/drm-uapi.rst b/Documentation/gpu/drm-uapi.rst
index 69f72e71a96e..826abe265a24 100644
--- a/Documentation/gpu/drm-uapi.rst
+++ b/Documentation/gpu/drm-uapi.rst
@@ -446,6 +446,21 @@ telemetry information (devcoredump, syslog). This is useful because the first
 hang is usually the most critical one which can result in consequential hangs or
 complete wedging.
 
+App information
+---------------
+
+The information about which application (if any) caused the device to get in the
+wedge state is useful for userspace if they want to notify the user about what
+happened (e.g. the compositor display a message to the user "The <app name>
+caused a graphical error and the system recovered") or to implement policies
+(e.g. the daemon may "ban" an app that keeps resetting the device). If the app
+information is not available, the uevent will display as ``PID=-1`` and
+``APP=none``. Otherwise, ``PID`` and ``APP`` will advertise about the guilty
+app.
+
+The reliability of this information is driver and hardware specific, and should
+be taken with a caution regarding it's precision.
+
 Consumer prerequisites
 ----------------------
 
-- 
2.49.0


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ