Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Date:   Wed, 31 Oct 2018 16:36:01 +0000
From:   Al Viro <viro@ZenIV.linux.org.uk>
To:     "Eric W. Biederman" <ebiederm@xmission.com>
Cc:     Linus Torvalds <torvalds@linux-foundation.org>,
        linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [git pull] mount API series
Message-ID: <20181031163601.GR32577@ZenIV.linux.org.uk>
References: <20181031053355.GQ32577@ZenIV.linux.org.uk>
 <87a7mut9cm.fsf@xmission.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <87a7mut9cm.fsf@xmission.com>
User-Agent: Mutt/1.9.1 (2017-09-22)
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

On Wed, Oct 31, 2018 at 10:38:17AM -0500, Eric W. Biederman wrote:
> A couple of bugs that I can see quickly.  Several of which I have
> previously reported:
> 
> - There is an easily triggered NULL pointer deference with open_tree
>   and mount propagation.

What the hell?  If the fixes that went in do not handle something,
especially if you have testcases, where the fuck have you been and
where _are_ those testcases, while we are at it?

Eric, this is bloody ridiculous - "I have an easily triggered NULL pointer
dereference in..., here it is" is hard to miscommunicate.  Sure, any such
needs to be fixed.  For crying out loud, that thing has not been hidden -
it sat in -next, it's been reposted several times...

I'm glad that you can see bugs.  How about _showing_ them?  Because I don't
see anything that would prevent this reply of yours from being posted
pretty much verbatim cycle after cycle, no matter what gets done.