From nobody Sat Oct 4 09:37:18 2025 Received: from galois.linutronix.de (Galois.linutronix.de [193.142.43.55]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id D852930FF21; Tue, 19 Aug 2025 07:17:33 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=193.142.43.55 ARC-Seal: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1755587855; cv=none; b=dnVR5Bkv0Z+B77xruqbfL6Yw3fhcai62dBI2bD6sC0aljzAaN5q6wDBE/oSQYMU2Kg/jTmZ6afgSF+Yt21HzOawSvEW4WXFe25iJ/eMuCu2DQeLRDS2i70AXOllHVI+xv/HPK3od1hQzAvAA2rR/OlqYt0fjfO2cuURp0CBcZX0= ARC-Message-Signature: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1755587855; c=relaxed/simple; bh=EBdHFltwlx7q2bFNVo6CBzKmW1i6ihD2pk/pvADqwi0=; h=From:To:Cc:Subject:Date:Message-ID:In-Reply-To:References: MIME-Version; b=ZH7yhKr6vnOu7CIYvtS/26MPE2F+3JJkIIKQQws5pXsUH9WnFDxwlspyiTGuTSh8uCr0MkPfiSdgYFo6Rto8zIDFpdjOdZY33eWdKHglKZJ0ShgG4zptEZmA35b7bDbdCodyw1j3HC1QrFRN2jtjwOmM3edittTAan0q3LLa64s= ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linutronix.de; spf=pass smtp.mailfrom=linutronix.de; dkim=pass (2048-bit key) header.d=linutronix.de header.i=@linutronix.de header.b=wJSNRSGY; dkim=permerror (0-bit key) header.d=linutronix.de header.i=@linutronix.de header.b=xE+qO/vs; arc=none smtp.client-ip=193.142.43.55 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linutronix.de Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=linutronix.de Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=linutronix.de header.i=@linutronix.de header.b="wJSNRSGY"; dkim=permerror (0-bit key) header.d=linutronix.de header.i=@linutronix.de header.b="xE+qO/vs" From: Sebastian Andrzej Siewior DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linutronix.de; s=2020; t=1755587852; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=bipLmqlQqujs91BW8T0MMUYQj3oxqWePKHlhg0j6rFE=; b=wJSNRSGYnNYG8uD1dBnV8/JiwsNZzrDZFf3qQZqQhnVr21G8TeCAr3gP7MWfifK0oy8B0Q rL98CGX2T4UugOIvZ78RGXlnlBXnJeC1CK8ijniEzrku7y2i3lIJ6/W5CpgnbNfGTlMxbb 29/X6ncNpaFgKR0e1qXKedPNgDXmIWDL5gremLiuLaGPoNifgZ4h0auN5sybi8uwnOCA+K 6Kv21BICnwvn6HdwBM8EAgmVH9lwImeQ8g1wFEA1n1w1PIdEU7584PxJFwl1Q6qNLwtgDU cpHn+Jg327z7CobbH5S8EtbgGYVgIxybhywaU+fjffK0JcSZLH1fxoRom/dcsg== DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=linutronix.de; s=2020e; t=1755587852; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=bipLmqlQqujs91BW8T0MMUYQj3oxqWePKHlhg0j6rFE=; b=xE+qO/vslAvP2chUEcNRiGOYzhku27+vRO1EtvNJs7Jkv5uFqD5tkDjrdSh3qt3anay9wK 5WQWnC9665vHc8Dw== To: linux-kernel@vger.kernel.org, linux-man@vger.kernel.org Cc: Alejandro Colomar , =?UTF-8?q?Andr=C3=A9=20Almeida?= , Darren Hart , Davidlohr Bueso , Ingo Molnar , Juri Lelli , Peter Zijlstra , Thomas Gleixner , Valentin Schneider , Waiman Long , Sebastian Andrzej Siewior Subject: [PATCH v5 1/3] man/man2const/PR_FUTEX_HASH.2const: Update as of Linux v6.17-rc2 Date: Tue, 19 Aug 2025 09:17:26 +0200 Message-ID: <20250819071728.1431543-2-bigeasy@linutronix.de> In-Reply-To: <20250819071728.1431543-1-bigeasy@linutronix.de> References: <20250819071728.1431543-1-bigeasy@linutronix.de> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="utf-8" The PR_FUTEX_HASH prctl interface was updated shortly before the release of v6.16. The changes are: - the functionality was disabled in v6.16 and enabled v6.17-rc1 after some updates the address performance concerns. - the "IMMUTABLE" functionality was removed. Update the page accordingly. Signed-off-by: Sebastian Andrzej Siewior --- man/man2const/PR_FUTEX_HASH.2const | 7 ++----- 1 file changed, 2 insertions(+), 5 deletions(-) diff --git a/man/man2const/PR_FUTEX_HASH.2const b/man/man2const/PR_FUTEX_HA= SH.2const index b500c943bf2cb..bc05226cd1594 100644 --- a/man/man2const/PR_FUTEX_HASH.2const +++ b/man/man2const/PR_FUTEX_HASH.2const @@ -44,7 +44,7 @@ since random processes can share in-kernel locks and it is not deterministic which process will be involved. .P -Linux 6.16 implements a process-wide private hash which is used by all +Linux 6.17 implements a process-wide private hash which is used by all .BR futex (2) operations that specify the .B FUTEX_PRIVATE_FLAG @@ -68,8 +68,6 @@ The value in .I op is one of the options below. .TP -.B PR_FUTEX_HASH_GET_IMMUTABLE -.TQ .B PR_FUTEX_HASH_GET_SLOTS .TQ .B PR_FUTEX_HASH_SET_SLOTS @@ -82,10 +80,9 @@ is set to indicate the error. .SH STANDARDS Linux. .SH HISTORY -Linux 6.16. +Linux 6.17. .SH SEE ALSO .BR prctl (2), .BR futex (2), -.BR PR_FUTEX_HASH_GET_IMMUTABLE (2const), .BR PR_FUTEX_HASH_GET_SLOTS (2const), .BR PR_FUTEX_HASH_SET_SLOTS (2const) --=20 2.50.1