linux-kernel - [PATCH 00/23] ipmi: Remove SRCU and handle the fallout

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: <20250424165020.627193-1-corey@minyard.net>
Date: Thu, 24 Apr 2025 11:49:37 -0500
From: Corey Minyard <corey@...yard.net>
To: linux-kernel@...r.kernel.org,
	openipmi-developer@...ts.sourceforge.net,
	Rik van Riel <riel@...riel.com>
Cc: "Paul E . McKenney" <paulmck@...nel.org>,
	Breno Leitao <leitao@...ian.org>
Subject: [PATCH 00/23] ipmi: Remove SRCU and handle the fallout

This patch set switches from SRCU to using normal locks.  This required
pulling most of the IPMI message handler up to run in kernel threads,
which was a good thing, anyway.  It also handles some fallout from
that change.

I didn't have a way to thoroughly test the IPMI driver, most of the
work for this was creating a test framework, which required work in
QEMU, the OpenIPMI simulator, and a few other things.  But that's
working now, and it shook out surprisingly few bugs, one in the new
changes and one driver unload issue.

Anyway, here's the first candidate for this.