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 1DC141C3C08; Mon, 23 Feb 2026 16:43:18 +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=1771865002; cv=none; b=Pz/t/Ig5iGh2hxerbOomjnVphXAPiGUPzUiA4jZN1BjCFZUSeQ+bhGeW5Dk640kqe3h/xRDtW8DqKOA7gS0NTB0FoK6wn36D/8twSWmEVueluhpkN56vFO3nTYMP6GXm8vVaNccwwuBIvo03h5091+Wao2nzrca99iHhZifgfio= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1771865002; c=relaxed/simple; bh=qtDr+aFQmyRgNg7N5Ok+7BM4Szik93lbZP+gD9/tIwk=; h=From:To:Cc:Subject:In-Reply-To:References:Date:Message-ID: MIME-Version:Content-Type; b=ZP2BTRpbtT+ggxsUtz3QEK6PVRxzRy/VIn2VczxijXTo7IToZ5bjwsw8EyDup3uZyeWP3/BltSseY50Mqcya1WZRnJ/TY64EXfFRL0KzedVCRn13nP3Kl3rFZZ7eirqn7O0Nf69FS4SY0Xwvsc7PJV/aDlA1JrorxS82u3SRZTM= 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=EdJsEJA5; 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="EdJsEJA5" DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=igalia.com; s=20170329; h=Content-Transfer-Encoding:Content-Type:MIME-Version:Message-ID: Date:References:In-Reply-To:Subject:Cc:To:From: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=2GKRN5XvDP26mqQnbzXys2FxqUf2pJih5vywszULBwk=; b=EdJsEJA5KglMlR+xlWSJbS3evg IifS0bx8jjuZBb3a4O2eL5XJzYgxkMDZBHO3DL4xQ1SRFPa0VKMKHrjMeqipkvMnMq9NJl/nL5Og5 C11orKQV/jepeI2kTphEPwKiJ7z+Ktj18bIy8n1G/lHBjse8SfqdG7mrUnfRSlAwD+tVEL3qQyqKs 5rgmNzbTNi8WvelA8bpzP1OOHqQApBKWcY7HVqKY20BI+ZFtess7Ji3D1j0SN4pPLT85EbtMPkkSb eCN9NP9P/NohDTwqcrzD9dB5jL+MNNbv8PFmadDivPzkuqZvXtFL9x99VeMeNyWlAsIFrj9T1IIkj 1wKuY7uQ==; Received: from bl17-145-117.dsl.telepac.pt ([188.82.145.117] helo=localhost) by fanzine2.igalia.com with utf8esmtpsa (Cipher TLS1.3:ECDHE_SECP256R1__RSA_PSS_RSAE_SHA256__AES_256_GCM:256) (Exim) id 1vuZ1W-004Kcj-GU; Mon, 23 Feb 2026 17:43:06 +0100 From: Luis Henriques To: Miklos Szeredi Cc: Bernd Schubert , Horst Birthelmer , Jim Harris , linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org, mgurtovoy@nvidia.com, ksztyber@nvidia.com Subject: Re: [PATCH] fuse: skip lookup during atomic_open() when O_CREAT is set In-Reply-To: (Miklos Szeredi's message of "Mon, 23 Feb 2026 16:53:33 +0100") References: <20260220204102.21317-1-jiharris@nvidia.com> Date: Mon, 23 Feb 2026 16:43:06 +0000 Message-ID: <874in7wgv9.fsf@wotan.olymp> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On Mon, Feb 23 2026, Miklos Szeredi wrote: > On Mon, 23 Feb 2026 at 16:37, Bernd Schubert wrote: > >> After the discussion about LOOKUO_HANDLE my impression was actually that >> we want to use compounds for the atomic open. > > I think we want to introduce an atomic operation that does a lookup + > an optional mknod, lets call this LOOKUP_CREATE_FH, this would return > a flag indicating whether the file was created or if it existed prior > to the operation. > > Then, instead of the current CREATE operation there would be a > compound with LOOKUP_CREATE_FH + OPEN. > > Does that make sense? FWIW, what I've been doing is something slightly different. I have been working on implementing MKOBJ_HANDLE+STATX+OPEN. And the plan was to rely on the compound flags, leaving it to user-space to handle the atomicity (e.g. MKOBJ_HANDLE would fail if O_EXCL was set). I was hoping to share a draft of this very soon, though it's still incomplete. For example, not all required compound operations are already implemented, most notably readdirplus! Cheers, --=20 Lu=C3=ADs