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=-3.8 required=3.0 tests=BAYES_00,DKIM_INVALID, DKIM_SIGNED,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS,URIBL_BLOCKED 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 B18B6C433DF for ; Tue, 11 Aug 2020 14:47:58 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 895FC2078E for ; Tue, 11 Aug 2020 14:47:58 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=fail reason="key not found in DNS" (0-bit key) header.d=szeredi.hu header.i=@szeredi.hu header.b="b/1GrCuy" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728895AbgHKOr4 (ORCPT ); Tue, 11 Aug 2020 10:47:56 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:53678 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728821AbgHKOry (ORCPT ); Tue, 11 Aug 2020 10:47:54 -0400 Received: from mail-ej1-x643.google.com (mail-ej1-x643.google.com [IPv6:2a00:1450:4864:20::643]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 67CC0C061787 for ; Tue, 11 Aug 2020 07:47:54 -0700 (PDT) Received: by mail-ej1-x643.google.com with SMTP id qc22so13392429ejb.4 for ; Tue, 11 Aug 2020 07:47:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=szeredi.hu; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=NlI3wwMv00NWAKa4U5L5YIW/C1hPZtgfWHscUycMhMg=; b=b/1GrCuy3zsT+xu5hfBEofJfyyKQre91pqNlsX0MOiaTmfxSPwy7IGLslRBMr1FYKY zI3t+/pBjNn/cWUYAhxg2ybd+V693B7WeKqrlAhEyzJ+Wc8nUDESQI2IF1QON3Jh9uVT YZ8yQWu+czbgj3GVSDUvltitl5HM0LYJ+TUMs= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=NlI3wwMv00NWAKa4U5L5YIW/C1hPZtgfWHscUycMhMg=; b=XBRA1NvN73JdQG1lx1Sf6LYpYTTNUXvCC3K+RVckZyjl88TGrHGlbBJctzcxO3J9pu nn/8T/2z262lAI+y9ILFsPZZoOpAWHbXhBrmwQlu8TeXWXu4b4LVGDR8onbSUkslSIgI rmX+fwVGVze4L8/yOBJyYny4KrGCyjm858bNEg8RAbGZz46hgXNZyosuUg8g5aD64vDm o2yrRoiJXDpGRL9moOCIZzmxupQsYe5SRhhmDXrP5EpnlZ5GUKkcT0BQFv1CfY6JOIMH nWgM1+Y8bJ44TJAh4yGoUJHOZWBUisHRXk6VjO+pFLRPMY7LTfjor9LrpVi55UGhKVUE 1+CQ== X-Gm-Message-State: AOAM532+ubK0sCrr1VH630NpNctkBvxRJ2Y+4+2WUZ/tQ7QSxW8mUeMo k6a/0Lf5ysHqzueKw+4L7oGTSw5Lz42JQycXQhG+gA== X-Google-Smtp-Source: ABdhPJyzKi8DHXr7w4yVAeEpF1qKnBzFBfVBk8wgiswCZWAR8v6h3A2J/MoGxuGyvmtaDdoLAlCOJpZxXZxjkYlm3EU= X-Received: by 2002:a17:906:3c59:: with SMTP id i25mr26135160ejg.202.1597157272920; Tue, 11 Aug 2020 07:47:52 -0700 (PDT) MIME-Version: 1.0 References: <1845353.1596469795@warthog.procyon.org.uk> <20200811135419.GA1263716@miu.piliscsaba.redhat.com> <20200811140833.GH1236603@ZenIV.linux.org.uk> <20200811143107.GI1236603@ZenIV.linux.org.uk> <20200811144247.GK1236603@ZenIV.linux.org.uk> In-Reply-To: <20200811144247.GK1236603@ZenIV.linux.org.uk> From: Miklos Szeredi Date: Tue, 11 Aug 2020 16:47:41 +0200 Message-ID: Subject: Re: file metadata via fs API (was: [GIT PULL] Filesystem Information) To: Al Viro Cc: linux-fsdevel@vger.kernel.org, David Howells , Linus Torvalds , Karel Zak , Jeff Layton , Miklos Szeredi , Nicolas Dichtel , Christian Brauner , Lennart Poettering , Linux API , Ian Kent , LSM , linux-kernel@vger.kernel.org Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Aug 11, 2020 at 4:42 PM Al Viro wrote: > > On Tue, Aug 11, 2020 at 04:36:32PM +0200, Miklos Szeredi wrote: > > > > > - strip off trailing part after first instance of /// > > > > - perform path lookup as normal > > > > - resolve meta path after /// on result of normal lookup > > > > > > ... and interpolation of relative symlink body into the pathname does change > > > behaviour now, *including* the cases when said symlink body does not contain > > > that triple-X^Hslash garbage. Wonderful... > > > > Can you please explain? > > Currently substituting the body of a relative symlink in place of its name > results in equivalent pathname. Except proc symlinks, that is. > With your patch that is not just no longer > true, it's no longer true even when the symlink body does not contain that > /// kludge - it can come in part from the symlink body and in part from the > rest of pathname. I.e. you can't even tell if substitution is an equivalent > replacement by looking at the symlink body alone. Yes, that's true not just for symlink bodies but any concatenation of two path segments. That's why it's enabled with RESOLVE_ALT. I've said that I plan to experiment with turning this on globally, but that doesn't mean it's necessarily a good idea. The posted patch contains nothing of that sort. Thanks, Miklos