From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from fanzine2.igalia.com (fanzine2.igalia.com [213.97.179.56]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id BBA87355057 for ; Fri, 9 Jan 2026 08:56:06 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=213.97.179.56 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1767948972; cv=none; b=YWbqsWRy0NvRQ+46YP4AvTAlt318q5SLK9HTu1o+Wjmc/05d0jz/DooQlaZfiu8u22g1BeMA7CMUSuQxCxwBVENgkwrMo47H9l+CPIRyiWdkfqInxZwUOrrV96IYjTMeu7PjdX0sTZH/D/ThODUSp7kwPzV/At/WKvMKLkm5PKg= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1767948972; c=relaxed/simple; bh=zZEBGC/AySVLndsfNIpJMwHMtFyvj/F22r1GQKRB2Xc=; h=Message-ID:Date:MIME-Version:Subject:To:Cc:References:From: In-Reply-To:Content-Type; b=HbzdH6MaOAAJlO3vu8ncQvoKbVqF8Nh+21j0S7AQUdnIf9y3YAo9+QhO9Z2Zw0hOgZbhuLyiTH1kdo42TSYVh065ooS/n/hiAwghAzT7F55W/1XS4Vo3W6iTHoqiG5vChXzXLyViJeVCIY1G/gnV28Au19+ym0PuMFYVDWh9K/8= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=igalia.com; spf=pass smtp.mailfrom=igalia.com; dkim=pass (2048-bit key) header.d=igalia.com header.i=@igalia.com header.b=OxnmN0ZE; arc=none smtp.client-ip=213.97.179.56 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=igalia.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=igalia.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=igalia.com header.i=@igalia.com header.b="OxnmN0ZE" DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=igalia.com; s=20170329; h=Content-Transfer-Encoding:Content-Type:In-Reply-To:From: References:Cc:To:Subject:MIME-Version:Date:Message-ID:Sender:Reply-To: Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender: Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=fTEki+a4dZq+PCarkxxwEYFqCoPGr+kqWvm5RiTwHrc=; b=OxnmN0ZElZ7RFX9XFmmcsq8Iwu lrsbSFYKPohVHaCQ8g0+gNBMq0R5oRbmpcCYKsBHH8oZDVqh6U61osahOtd+l/212BphavtR/+AXi zPSGKtcnm3/RQchiRKIWnNsmnpH9CcmcMGsbeZbECldXcgmuU8ps/wtNDij7bfDeCGlxHz/WSBlvg IWAWVVSM29O8v2BpVG3M4DxBZaRY8qfjdbZ5ff5q1VhsIFeuT1BmgxcY3wnuX3ky6idkYBGwkn0/p DCLU6HdR/5cCaEwGhDhHtVQkRJb3EmqsJZEzzu/e1jlWtz9i87qB3yWyEhloQ8OgS6HoTe1vMF23E D3FVVO6g==; Received: from [90.240.106.137] (helo=[192.168.0.101]) by fanzine2.igalia.com with esmtpsa (Cipher TLS1.3:ECDHE_X25519__RSA_PSS_RSAE_SHA256__AES_128_GCM:128) (Exim) id 1ve8HS-003KbE-Er; Fri, 09 Jan 2026 09:55:38 +0100 Message-ID: Date: Fri, 9 Jan 2026 08:55:37 +0000 Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: [PATCH 0/2] drm/panic: Avoid crash from invalid CONFIG_DRM_PANIC_SCREEN values To: Nathan Chancellor , Jocelyn Falempe , Javier Martinez Canillas , Maarten Lankhorst , Maxime Ripard , Thomas Zimmermann Cc: dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org References: <20260105-drm_panic-handle-invalid-drm_panic_screen-v1-0-55228bd4b0f8@kernel.org> Content-Language: en-GB From: Tvrtko Ursulin In-Reply-To: <20260105-drm_panic-handle-invalid-drm_panic_screen-v1-0-55228bd4b0f8@kernel.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit On 06/01/2026 06:19, Nathan Chancellor wrote: > Hi all, > > This series addresses a couple of issues I noticed when accessing > /sys/module/drm/parameters/panic_screen on my Arch Linux machines, which > have "qr_code" as the value of CONFIG_DRM_PANIC_SCREEN. This happened to > be unsupported in my configuration since I was missing some Rust > dependencies in my environment for CONFIG_DRM_PANIC_SCREEN_QR_CODE, > resulting in a kernel crash. Patch one addresses the root cause of the > crash and patch two addresses an inconsistency I noticed between this > new code and the documented value for CONFIG_DRM_PANIC_SCREEN in Kconfig > for qr_code. > > If there are any issues, please let me know. I've pushed the series to drm-misc-next, thanks for fixing it up! Regards, Tvrtko > > --- > Nathan Chancellor (2): > drm/panic: Ensure drm_panic_type is initialized to a valid value > drm/panic: Fix expected string for QR_CODE in drm_panic_type_map > > drivers/gpu/drm/drm_panic.c | 11 +++++++---- > 1 file changed, 7 insertions(+), 4 deletions(-) > --- > base-commit: 349d4efadc1f831ebc0b872ba1e3a2b7dd58b72b > change-id: 20260105-drm_panic-handle-invalid-drm_panic_screen-097e49e21c49 > > Best regards, > -- > Nathan Chancellor >