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, 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 72032C433E2 for ; Fri, 28 Aug 2020 21:34:55 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 5A77220838 for ; Fri, 28 Aug 2020 21:34:55 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726928AbgH1Vev (ORCPT ); Fri, 28 Aug 2020 17:34:51 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:37402 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726033AbgH1Veu (ORCPT ); Fri, 28 Aug 2020 17:34:50 -0400 Received: from ZenIV.linux.org.uk (zeniv.linux.org.uk [IPv6:2002:c35c:fd02::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 2976CC061264; Fri, 28 Aug 2020 14:34:50 -0700 (PDT) Received: from viro by ZenIV.linux.org.uk with local (Exim 4.92.3 #3 (Red Hat Linux)) id 1kBm1F-006cEb-JF; Fri, 28 Aug 2020 21:34:45 +0000 Date: Fri, 28 Aug 2020 22:34:45 +0100 From: Al Viro To: Florian Margaine Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH] fs: allow do_renameat2() over bind mounts of the same filesystem. Message-ID: <20200828213445.GM1236603@ZenIV.linux.org.uk> References: <871rjqh5bw.fsf@platform.sh> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <871rjqh5bw.fsf@platform.sh> Sender: linux-fsdevel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-fsdevel@vger.kernel.org On Fri, Aug 28, 2020 at 10:40:35PM +0200, Florian Margaine wrote: > There's currently this seemingly unnecessary limitation that rename() > cannot work over bind mounts of the same filesystem, ... is absolutely deliberate - that's how you set a boundary in the tree, preventing both links and renames across it. Incidentally, doing that would have fun effects for anyone with current directory inside the subtree you'd moved - try and see.