linux-kernel - Re: In-kernel parser for the BMOF format used by WMI-ACPI

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: <20250311201357.tyldll7j2eogmryw@pali>
Date: Tue, 11 Mar 2025 21:13:57 +0100
From: Pali Rohár <pali@...nel.org>
To: Armin Wolf <W_Armin@....de>
Cc: "linux@...ssschuh.net" <linux@...ssschuh.net>,
	Kurt Borja <kuurtb@...il.com>, akpm@...ux-foundation.org,
	mcgrof@...nel.org, russ.weight@...ux.dev, dakr@...nel.org,
	"platform-driver-x86@...r.kernel.org" <platform-driver-x86@...r.kernel.org>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: In-kernel parser for the BMOF format used by WMI-ACPI

On Tuesday 11 March 2025 21:06:16 Armin Wolf wrote:
>  - Is there any way to check whether the Doublespace compression algorithm is still encumbered by patents?

Linux kernel 2.2 or 2.4 had full read/write support for doublespace
compression algorithm in mainline kernel and it was connected with fat
driver. IIRC it was dropped for kernel 2.6 because nobody ported that
vfat code to new fs API and hence doublespace in-kernel compression
algorithm was not needed/used anymore. But I do not remember details.

So IMHO it should not be a problem to reintroduce same code into kernel
again if there is a new need for it.

And in my project I reused the doublespace compression code from old
Linux kernel.