From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from fanzine2.igalia.com (fanzine2.igalia.com [213.97.179.56]) (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 6C85D5C9E for ; Tue, 31 Mar 2026 12:59:39 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=213.97.179.56 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1774961982; cv=none; b=cwmfAsAt+l/unQZyjNA3lyOV/Brp5jy/MaQ4Wl0r3kLRC8qixnAsaEwRIooTxeOtDxihT1Tg5yMP5p07c5qkb4gC7wyRbGsdfKpzrOKtwQimXDV9fUk/U3H2cSADdBSG7FKOCc4Z8w7AqluhvZWTcOTVQm7A5OA5HP0TniY4HiI= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1774961982; c=relaxed/simple; bh=/jgYzUf2ky0EO5udWN83aif+fKB/X7qM7r/e8feBjIg=; h=Message-ID:Date:MIME-Version:Subject:To:Cc:References:From: In-Reply-To:Content-Type; b=WZh4qXyMe9w/N04dTG6FF5nhe+jHYWduKpcWLkfP9fi7Ilhs9YVMTkS5u+Q3kyyG2xvBmYBTOWl9D1BPnoySdq3YX4pkhGiPFo05SVmxzp9OOHc/PsErpmPCIL/1CLdzSlSYM0qnq/XxFZfc0RJaSJvMlZDTKN7Jcc/Jq89r2iA= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=igalia.com; spf=pass smtp.mailfrom=igalia.com; dkim=pass (2048-bit key) header.d=igalia.com header.i=@igalia.com header.b=j3KdkGUd; arc=none smtp.client-ip=213.97.179.56 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=igalia.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=igalia.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=igalia.com header.i=@igalia.com header.b="j3KdkGUd" DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=igalia.com; s=20170329; h=Content-Transfer-Encoding:Content-Type:In-Reply-To:From: References:Cc:To:Subject:MIME-Version:Date:Message-ID:Sender:Reply-To: Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender: Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=Ib1SUAoeUT8Ziku2/tcN5tDFfSCD/fNCyYMyAjFw/6g=; b=j3KdkGUdPEhBtJ57306bW/m7cd 8Z0SzpbSeaQY2jtSdDH85B1AtlFSUsvw3NHU23MCM9lu2ZJrMuQVH23cBL7qVmNg0/hJak8oPJAzD 57yCdLkAXoaQcZRWUUbJIEyIrM6GtxySU6u5GAibKjmrXkC7TqtPupTJfce4dDbFmw0yxcAq7NeKv PV6h9crKOcwlU1Bt45OJU3NFrg5Xu6juZcAC0dpunIS+QiwZNRlubXOpYXSHtpvD384R4NOY5Cyt9 FPaTxArG8YOhmtoPngdbmm5j5DT9ZKPX0VW9e4XdKkuzhUtlf92J0c3W81pPF0kBX8nIOeus2SCmI v3H4ytag==; Received: from [187.57.76.124] (helo=[192.168.15.100]) by fanzine2.igalia.com with esmtpsa (Cipher TLS1.3:ECDHE_X25519__RSA_PSS_RSAE_SHA256__AES_128_GCM:128) (Exim) id 1w7Ygn-009SVn-Td; Tue, 31 Mar 2026 14:59:26 +0200 Message-ID: <258bb8bb-72eb-4e72-8591-b1e121da7141@igalia.com> Date: Tue, 31 Mar 2026 09:59:17 -0300 Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Beta Subject: Re: [patch V3 00/14] futex: Address the robust futex unlock race for real To: Mark Rutland Cc: LKML , Mathieu Desnoyers , Sebastian Andrzej Siewior , Carlos O'Donell , Peter Zijlstra , Florian Weimer , Rich Felker , Torvald Riegel , Darren Hart , Ingo Molnar , Davidlohr Bueso , Arnd Bergmann , "Liam R . Howlett" , Uros Bizjak , =?UTF-8?Q?Thomas_Wei=C3=9Fschuh?= , Thomas Gleixner References: <20260330114212.927686587@kernel.org> Content-Language: en-US From: =?UTF-8?Q?Andr=C3=A9_Almeida?= In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Hey Mark, Em 30/03/2026 10:45, Mark Rutland escreveu: > On Mon, Mar 30, 2026 at 02:01:58PM +0200, Thomas Gleixner wrote: >> >> 2) VDSO based unlock and pointer clearing helpers with a fix-up function >> in the kernel when user space was interrupted within the critical >> section. > > I see the vdso bits in this series are specific to x86. Do other > architectures need something here? > > I might be missing some context; I'm not sure whether that's not > necessary or just not implemented by this series, and so I'm not sure > whether arm64 folk and other need to go dig into this. > If you haven't done it yet, I would like to give a shot to implement the arm64 version of the vDSO.