From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-0.9 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id D328BC3F2D2 for ; Mon, 2 Mar 2020 14:30:35 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id A55B9222C4 for ; Mon, 2 Mar 2020 14:30:35 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=redhat.com header.i=@redhat.com header.b="aS6sx/Kq" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727196AbgCBOad (ORCPT ); Mon, 2 Mar 2020 09:30:33 -0500 Received: from us-smtp-1.mimecast.com ([207.211.31.81]:30367 "EHLO us-smtp-delivery-1.mimecast.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1727085AbgCBOad (ORCPT ); Mon, 2 Mar 2020 09:30:33 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1583159432; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=4g9ejPyZjnXkSrIMqykLr/Nbkbvn0R1XhqNJLqCOnUc=; b=aS6sx/Kq81kbrlgFIHV2wvWI5gr8AIKb8b+oCli01szGpU3Idgt9895oCIUoQrhu+Eazij C8cNCA4llDPr5LfU4a66Efi5nXqE6SYfgKaPJ59u7dpD2Jr1HPTRxosu6/8mWglC5uqCVw 9Uef1B4PRs796pzTfPD1H1vGlpIG1fM= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-197-gXhPO-zzMAOf_Chrw4ZSrA-1; Mon, 02 Mar 2020 09:30:28 -0500 X-MC-Unique: gXhPO-zzMAOf_Chrw4ZSrA-1 Received: from smtp.corp.redhat.com (int-mx02.intmail.prod.int.phx2.redhat.com [10.5.11.12]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 45349DB61; Mon, 2 Mar 2020 14:30:26 +0000 (UTC) Received: from warthog.procyon.org.uk (ovpn-120-182.rdu2.redhat.com [10.10.120.182]) by smtp.corp.redhat.com (Postfix) with ESMTP id 7A95160BF7; Mon, 2 Mar 2020 14:30:24 +0000 (UTC) Organization: Red Hat UK Ltd. Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod Street, Windsor, Berkshire, SI4 1TE, United Kingdom. Registered in England and Wales under Company Registration No. 3798903 From: David Howells In-Reply-To: <87h7z7ngd4.fsf@oldenburg2.str.redhat.com> References: <87h7z7ngd4.fsf@oldenburg2.str.redhat.com> <96563.1582901612@warthog.procyon.org.uk> <20200228152427.rv3crd7akwdhta2r@wittgenstein> To: Florian Weimer Cc: dhowells@redhat.com, Christian Brauner , linux-api@vger.kernel.org, viro@zeniv.linux.org.uk, metze@samba.org, torvalds@linux-foundation.org, cyphar@cyphar.com, linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: Have RESOLVE_* flags superseded AT_* flags for new syscalls? MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <859018.1583159423.1@warthog.procyon.org.uk> Date: Mon, 02 Mar 2020 14:30:23 +0000 Message-ID: <859019.1583159423@warthog.procyon.org.uk> X-Scanned-By: MIMEDefang 2.79 on 10.5.11.12 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Florian Weimer wrote: > Regarding open flags, I think the key point for future APIs is to avoid > using the set of flags for both control of the operation itself > (O_NOFOLLOW/AT_SYMLINK_NOFOLLOW, O_NOCTTY) and properaties of the > resulting descriptor (O_RDWR, O_SYNC). I expect that doing that would > help code that has to re-create an equivalent descriptor. The operation > flags are largely irrelevant to that if you can get the descriptor by > other means. It would also be nice to sort out the problem with O_CLOEXEC. That can have a different value, depending on the arch - so it excludes at least three bits from the O_* flag set. David