From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-fsdevel-owner@vger.kernel.org>
Received: from out03.mta.xmission.com ([166.70.13.233]:50265 "EHLO
        out03.mta.xmission.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1726276AbeHZHDb (ORCPT
        <rfc822;linux-fsdevel@vger.kernel.org>);
        Sun, 26 Aug 2018 03:03:31 -0400
From: ebiederm@xmission.com (Eric W. Biederman)
To: Al Viro <viro@ZenIV.linux.org.uk>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
        dhowells@redhat.com, linux-fsdevel@vger.kernel.org,
        linux-api@vger.kernel.org
References: <20180823223145.GK6515@ZenIV.linux.org.uk>
Date: Sun, 26 Aug 2018 05:22:18 +0200
In-Reply-To: <20180823223145.GK6515@ZenIV.linux.org.uk> (Al Viro's message of
        "Thu, 23 Aug 2018 23:31:45 +0100")
Message-ID: <87va7xx15h.fsf@xmission.com>
MIME-Version: 1.0
Content-Type: text/plain
Subject: Re: [git pull] new mount API
Sender: linux-fsdevel-owner@vger.kernel.org
List-ID: <linux-fsdevel.vger.kernel.org>


Sigh.

I just noticed that this tree reintroduces bugs that were fixed with
cfb2f6f6e0ba ("Revert "mqueue: switch to on-demand creation of internal mount"")

So in addition to ongoing discussion about what the new mount api should
look like we have bugs in the implementation.  This really does not look
like this branch is ready to be merged yet.

Eric