linux-kernel - Re: [PATCH bpf-next v3 00/25] Resilient Queued Spin Lock

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

Message-ID: <CAP01T75iEw0mU6LeigHMp06DGsgZHp7UWY422xZtX1U7tVHa0Q@mail.gmail.com>
Date: Sat, 15 Mar 2025 00:49:51 +0100
From: Kumar Kartikeya Dwivedi <memxor@...il.com>
To: bpf@...r.kernel.org, linux-kernel@...r.kernel.org
Cc: Linus Torvalds <torvalds@...ux-foundation.org>, Peter Zijlstra <peterz@...radead.org>, 
	Will Deacon <will@...nel.org>, Waiman Long <llong@...hat.com>, Alexei Starovoitov <ast@...nel.org>, 
	Andrii Nakryiko <andrii@...nel.org>, Daniel Borkmann <daniel@...earbox.net>, 
	Martin KaFai Lau <martin.lau@...nel.org>, Eduard Zingerman <eddyz87@...il.com>, 
	"Paul E. McKenney" <paulmck@...nel.org>, Tejun Heo <tj@...nel.org>, Barret Rhoden <brho@...gle.com>, 
	Josh Don <joshdon@...gle.com>, Dohyun Kim <dohyunkim@...gle.com>, 
	linux-arm-kernel@...ts.infradead.org, kkd@...a.com, kernel-team@...a.com
Subject: Re: [PATCH bpf-next v3 00/25] Resilient Queued Spin Lock

On Mon, 3 Mar 2025 at 16:23, Kumar Kartikeya Dwivedi <memxor@...il.com> wrote:
>
>

Hello,

In v4, we will fix a couple of issues noticed in patchwork, where the
locktorture patch breaks bisection and needs to be ordered after the
Makefile change (patch 17 and 18 need to be swapped), but the biggest
change is that we will move rqspinlock implementation under
kernel/bpf/ to make it clear that it should be used by the BPF
subsystem only.

Thanks

>
> Introduction
> ------------
>
> This patch set introduces Resilient Queued Spin Lock (or rqspinlock with
> res_spin_lock() and res_spin_unlock() APIs).
>
> [...]