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=-2.9 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS,USER_AGENT_NEOMUTT autolearn=ham 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 60651C31E5B for ; Mon, 17 Jun 2019 18:52:14 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 2D8C22084D for ; Mon, 17 Jun 2019 18:52:14 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=brauner.io header.i=@brauner.io header.b="B+WUu6Cx" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726405AbfFQSwM (ORCPT ); Mon, 17 Jun 2019 14:52:12 -0400 Received: from mail-wm1-f68.google.com ([209.85.128.68]:51815 "EHLO mail-wm1-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725829AbfFQSwM (ORCPT ); Mon, 17 Jun 2019 14:52:12 -0400 Received: by mail-wm1-f68.google.com with SMTP id 207so522283wma.1 for ; Mon, 17 Jun 2019 11:52:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=brauner.io; s=google; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=pjVCWmNKxJeMAm6vkG2OfPRISxnV9sN5LGap4EcCEdo=; b=B+WUu6CxHD4qe+TlSAj2yNeYIMsbQe/yaBB02OkJTg5NiS3kyUv9Lp9FAJwZmSU0LE SVriiYqjv/UGUwQEVeOPpDNqrofNWxjCMOoCDFADZ0X7UpnM0vv0lHlX5LKHj4OpWQ6+ 6eJB84hV6fK4q2g58Ejmrpb0dkKy7EyiwfwhJ3iGxWICFQcYrQP8YweYI2xplosJMicO WWLd2d9/99gLwbz58RMjaNJOYeuKmG4BmVDV+jQwakD6hz7/nqVw2aa/fvYHR6rK6JPB atGlNfH7HiiMn5g3+kUddiBZKx1QedfnFavgp10cEfTPiGgUVgpuAwxvHIv8LSQoCk46 Uk7A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=pjVCWmNKxJeMAm6vkG2OfPRISxnV9sN5LGap4EcCEdo=; b=YBWmjBthC+gXFuofVFI8IIFiFCXsxoc9Ho2+VjmjbH5iUk/ZE7Y4hVD+s9y41HmDK4 tMG4aClyxhLqKCA+fT4Tzwjhwjn4AKGMIpj9iElSxdmhKEM8wNkZi4C/kAKTCUySSrQb x0It9Ztk9V3MaF8MQ0j09oKeEsrbfZtVSgRypSaK20QczSe7JuwJ0UPCycssPg5GRT1g DOleTUll5Uo1/QPwygcUlsOSWQATfv61ja+AbPSd0Mnyzg0wDlQOhubQ2oaOW94mnYR6 ipMQpZfsEv/DZhH0ljHXcs0zXOI6B/EKbStDhVHv7WZqg2K0lDxhSMKbquEkVNz1OQqU Me8A== X-Gm-Message-State: APjAAAWet5N/lmh1oXT6i1KxRK0wUVE9IXTeUQK52XuA1gn/nm0azBvD X7Lej0raedYWsNXlyT8/qISfkg== X-Google-Smtp-Source: APXvYqxYsUkV6LBwIvTZu2KJAp90AA0hqZy0BsFn4HMpQzgJAaJrC3xWXPFP641RvogUgHDt6YB8TA== X-Received: by 2002:a1c:c255:: with SMTP id s82mr91486wmf.6.1560797530287; Mon, 17 Jun 2019 11:52:10 -0700 (PDT) Received: from brauner.io ([212.91.227.56]) by smtp.gmail.com with ESMTPSA id j189sm86126wmb.48.2019.06.17.11.52.09 (version=TLS1_3 cipher=AEAD-AES256-GCM-SHA384 bits=256/256); Mon, 17 Jun 2019 11:52:09 -0700 (PDT) Date: Mon, 17 Jun 2019 20:52:09 +0200 From: Christian Brauner To: Linus Torvalds Cc: Al Viro , "Eric W. Biederman" , Linux List Kernel Mailing , linux-fsdevel , stable Subject: Re: [PATCH] fs/namespace: fix unprivileged mount propagation Message-ID: <20190617185208.3qij2fl7acwuewy3@brauner.io> References: <20190617184711.21364-1-christian@brauner.io> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: User-Agent: NeoMutt/20180716 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Jun 17, 2019 at 11:50:13AM -0700, Linus Torvalds wrote: > On Mon, Jun 17, 2019 at 11:47 AM Christian Brauner wrote: > > > > When propagating mounts across mount namespaces owned by different user > > namespaces it is not possible anymore to move or umount the mount in the > > less privileged mount namespace. > > I will wait a short while in the hope of getting Al's ack for this, > but since it looks about as good as it likely can be, I suspect I'll > just apply it later today even without such an ack.. Thanks! Note that I stupidly messed up whitespace by accidently adding an additional newline. I'll just send a v1 that fixes this nonsense. Christian