linux-kernel - [RFC PATCH v4 0/1] platform/x86/tuxedo: Add virtual LampArray for TUXEDO NB04

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: <20241001180658.76396-1-wse@tuxedocomputers.com>
Date: Tue,  1 Oct 2024 20:06:56 +0200
From: Werner Sembach <wse@...edocomputers.com>
To: 
Cc: bentiss@...nel.org,
	dri-devel@...ts.freedesktop.org,
	hdegoede@...hat.com,
	jelle@...aa.nl,
	jikos@...nel.org,
	lee@...nel.org,
	linux-input@...r.kernel.org,
	linux-kernel@...r.kernel.org,
	linux-leds@...r.kernel.org,
	miguel.ojeda.sandonis@...il.com,
	ojeda@...nel.org,
	onitake@...il.com,
	pavel@....cz,
	cs@...edo.de
Subject: [RFC PATCH v4 0/1] platform/x86/tuxedo: Add virtual LampArray for TUXEDO NB04

Just wanted to send my current state as previous version had a null pointer dereference.

On this toppic, why does hdev have a hdev->driver_data and a hdev->dev.driver_data which are not the same? I assume hdev->driver_data is for the ll_driver and hdev->dev.driver_data for the driver?