Received: by 2002:a25:c205:0:0:0:0:0 with SMTP id s5csp4210379ybf; Tue, 3 Mar 2020 22:57:10 -0800 (PST) X-Google-Smtp-Source: ADFU+vt+G002l2VMMSmLB95QPibI/FSv2fwFKGZodli0DW3oAUDtn6Y8cVIyp4nokQOcBQf2sX5w X-Received: by 2002:a05:6808:315:: with SMTP id i21mr755165oie.139.1583305030033; Tue, 03 Mar 2020 22:57:10 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1583305030; cv=none; d=google.com; s=arc-20160816; b=otqKtJH/OAug4PjyqqrG4M3+5l3h0kvlENW7SxAS5FGa9401zwzHQI3vEG7n+nRSNq w+bKr58jDeVKDWCe09ktCaMt8NXg2DFF+Y8gMn/HwbqRmPwOVDtg4PUzkBWcWBm9/zJh ofP6ohAGUhpRb9b/N48c4Ljiwa6hOoSSSpBSiJ0uN9Tx9z97wlADytmcsnRdYr3lbREi joHA9yTNLlHM1iDxg+UcXASjb+g18epYAiTZ2yHxCQ35na1Em7JnomjeeZAq28fvAe1t uf8cV8U7aJHmV0cGH1pujb7xrtkIMXOz/qY88Cke0/Jg/ubZnLD49aeoj/QTX5HeAm3w fp7g== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date; bh=ICUEsSq0Y4LFo2YQGPzjgInFbMslOlqCfXyDcDwprKk=; b=llG4Tq5mqJyfl6wLC45WrKG0A88hzXpBmwYE32Fo6aC5u+qaYeRbkSGQEDFAV7Am6T TtHhJAI3WmATbq+VmGzvxTbfdel/N/rKR1hamjUGoA4tzRaGvPH2IXY3iX+QZImzur5k 97yUcZNqV1CtDfPE+pddTOcelfzH8vxd9YJCXX97Apa23fllMeWHXvQAjaueMQnR/OXw o2hCTBwX1ugfEsJsW29OXHN2Xfus/4GE6ypqXzLUkonMQCUvSaHMhmdiFya8sceam0d0 mMqMsq9xI1T1yp9Xvr87wax+VPvddnIf/BcXBixSOHsvxiPLNc4FQIFoXrWQHJ68TEyb k26A== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id f2si682459oib.9.2020.03.03.22.56.57; Tue, 03 Mar 2020 22:57:10 -0800 (PST) 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; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728409AbgCDGzv (ORCPT + 99 others); Wed, 4 Mar 2020 01:55:51 -0500 Received: from zeniv.linux.org.uk ([195.92.253.2]:52406 "EHLO ZenIV.linux.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726957AbgCDGzu (ORCPT ); Wed, 4 Mar 2020 01:55:50 -0500 Received: from viro by ZenIV.linux.org.uk with local (Exim 4.92.3 #3 (Red Hat Linux)) id 1j9NwZ-004wMP-8p; Wed, 04 Mar 2020 06:55:47 +0000 Date: Wed, 4 Mar 2020 06:55:47 +0000 From: Al Viro To: "Eric W. Biederman" Cc: Linus Torvalds , linux-fsdevel , Linux Kernel Mailing List Subject: Re: [RFC][PATCHSET] sanitized pathwalk machinery (v3) Message-ID: <20200304065547.GP23230@ZenIV.linux.org.uk> References: <20200223011154.GY23230@ZenIV.linux.org.uk> <20200301215125.GA873525@ZenIV.linux.org.uk> <20200302003926.GM23230@ZenIV.linux.org.uk> <87o8tdgfu8.fsf@x220.int.ebiederm.org> <20200304002434.GO23230@ZenIV.linux.org.uk> <87wo80g0bo.fsf@x220.int.ebiederm.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <87wo80g0bo.fsf@x220.int.ebiederm.org> Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Mar 03, 2020 at 11:23:39PM -0600, Eric W. Biederman wrote: > Al Viro writes: > > > 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? > > > > Subject: [locking/qspinlock] 7b6da71157: unixbench.score 8.4% improvement > > seems to be the latest of that sort, > > From: kernel test robot > > > > Not sure how much of pathwalk-heavy loads is covered by profiling > > bots of that sort, unfortunately... ;-/ > > Do the xfs-tests cover that sort of thing? > The emphasis is stress testing the filesystem not the VFS but there is a > lot of overlap between the two. I do run xfstests. But "runs in KVM without visible slowdowns" != "won't cause them on 48-core bare metal". And this area (especially when it comes to RCU mode) can be, er, interesting in that respect. FWIW, I'm putting together some litmus tests for pathwalk semantics - one of the things I'd like to discuss at LSF; quite a few codepaths are simply not touched by anything in xfstests.