From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <SRS0=idZ5=4V=vger.kernel.org=linux-kernel-owner@kernel.org>
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=-0.8 required=3.0 tests=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 CD633C3F2C6
	for <linux-kernel@archiver.kernel.org>; Wed,  4 Mar 2020 00:24:40 +0000 (UTC)
Received: from vger.kernel.org (vger.kernel.org [209.132.180.67])
	by mail.kernel.org (Postfix) with ESMTP id A95A820842
	for <linux-kernel@archiver.kernel.org>; Wed,  4 Mar 2020 00:24:40 +0000 (UTC)
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1728366AbgCDAYj (ORCPT
        <rfc822;linux-kernel@archiver.kernel.org>);
        Tue, 3 Mar 2020 19:24:39 -0500
Received: from zeniv.linux.org.uk ([195.92.253.2]:48812 "EHLO
        ZenIV.linux.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1727865AbgCDAYj (ORCPT
        <rfc822;linux-kernel@vger.kernel.org>);
        Tue, 3 Mar 2020 19:24:39 -0500
Received: from viro by ZenIV.linux.org.uk with local (Exim 4.92.3 #3 (Red Hat Linux))
        id 1j9Hpy-004nPO-TA; Wed, 04 Mar 2020 00:24:35 +0000
Date:   Wed, 4 Mar 2020 00:24:34 +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 <linux-fsdevel@vger.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [RFC][PATCHSET] sanitized pathwalk machinery (v3)
Message-ID: <20200304002434.GO23230@ZenIV.linux.org.uk>
References: <20200223011154.GY23230@ZenIV.linux.org.uk>
 <20200301215125.GA873525@ZenIV.linux.org.uk>
 <CAHk-=wh1Q=H-YstHZRKfEw2McUBX2_TfTc=+5N-iH8DSGz44Qg@mail.gmail.com>
 <20200302003926.GM23230@ZenIV.linux.org.uk>
 <87o8tdgfu8.fsf@x220.int.ebiederm.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <87o8tdgfu8.fsf@x220.int.ebiederm.org>
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On Tue, Mar 03, 2020 at 05:48:31PM -0600, Eric W. Biederman wrote:

> > I hope it gets serious beating, though - it touches pretty much every
> > codepath in pathname resolution.  Is there any way to sic the bots on
> > a branch, short of "push it into -next and wait for screams"?
> 
> Last I looked pushing a branch to kernel.org was enough for the
> kbuild bots.  Sending patches to LKML is also enough for those bots.
> 
> I don't know if that kind of bot is what you need testing your code.

Build bots are generally nice, but in this case... pretty much all of
the changes are in fs/namei.c, which is not all that sensitive to
config/architecture/whatnot.  Sure, something like "is audit enabled?"
may affect the build problems, but not much beyond that.

What was that Intel-run(?) bot that posts "such-and-such metrics has
42% regression on such-and-such commit" from time to time?
<checks>
Subject: [locking/qspinlock] 7b6da71157: unixbench.score 8.4% improvement
seems to be the latest of that sort,
From: kernel test robot <rong.a.chen@intel.com>

Not sure how much of pathwalk-heavy loads is covered by profiling
bots of that sort, unfortunately... ;-/