linux-kernel - [PATCH v5 0/2] Alternative approach for boot

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-next>] [day] [month] [year] [list]

Message-ID: <20250722041051.3354121-1-superm1@kernel.org>
Date: Mon, 21 Jul 2025 23:10:49 -0500
From: Mario Limonciello <superm1@...nel.org>
To: David Airlie <airlied@...il.com>,
	Bjorn Helgaas <bhelgaas@...gle.com>
Cc: Alex Deucher <alexander.deucher@....com>,
	Christian König <christian.koenig@....com>,
	Simona Vetter <simona@...ll.ch>,
	Maarten Lankhorst <maarten.lankhorst@...ux.intel.com>,
	Maxime Ripard <mripard@...nel.org>,
	Thomas Zimmermann <tzimmermann@...e.de>,
	dri-devel@...ts.freedesktop.org (open list:DRM DRIVERS),
	linux-kernel@...r.kernel.org (open list),
	linux-pci@...r.kernel.org (open list:PCI SUBSYSTEM),
	Daniel Dadap <ddadap@...dia.com>,
	Mario Limonciello <mario.limonciello@....com>
Subject: [PATCH v5 0/2] Alternative approach for boot_display visibility

From: Mario Limonciello <mario.limonciello@....com>

The past few days there have been various discussions about what to do
with the boot_display sysfs file so that it doesn't need to be made so
late in startup.

Bjorn had an aha moment pointing out that there is no reason to "find"
the PCI device using screen_info_pci_dev() because the device is already
known.  Instead we just need to check if it has the screen resources.

This series adjusts the boot_display behavior to use that and then convert
boot_display into a static sysfs file that can be loaded when the device
is created without needing to change visibility.

This is an ALTERNATIVE to moving it to DRM, which is what v4 does [1].
Either solution can be picked up depending upon the collective decision
whether to keep boot_display file in PCI core or DRM core.

Link: https://lore.kernel.org/linux-pci/20250721185726.1264909-1-superm1@kernel.org/T/#me4356b3a172cbdafe83393bedce10f17a86e0da7

Mario Limonciello (2):
  fbcon: Stop using screen_info_pci_dev()
  PCI: Adjust visibility of boot_display attribute instead of creation

 arch/x86/video/video-common.c | 12 ++++++--
 drivers/pci/pci-sysfs.c       | 58 ++++++++++++-----------------------
 2 files changed, 30 insertions(+), 40 deletions(-)

-- 
2.48.1