Received: by 2002:a25:c593:0:0:0:0:0 with SMTP id v141csp50485ybe; Thu, 5 Sep 2019 17:15:34 -0700 (PDT) X-Google-Smtp-Source: APXvYqyGOwH00U79EsmA5d93BK6ec8E7G/ZyY8JZsD5/PRGdXCLyLdg4zanivbS55OCSKiWI+byz X-Received: by 2002:a63:bf01:: with SMTP id v1mr5480922pgf.278.1567728933839; Thu, 05 Sep 2019 17:15:33 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1567728933; cv=none; d=google.com; s=arc-20160816; b=dSGbFEvHgNz6ErzqTrJsSPYvflo89B7lRQPajpo2u+F8MDBrXxWS1AxgDijbbRtpbK dAgx/L8D6mrmdH7yuBSVQVZQQd07+SowlcJB7W9BBoKOoAFfJm7+q9xR8xShfSJkaL3o RrBHQDAzScP3D1UrkkZ6aSR1gVtTpuHp0rsDc14yaQJQwPzVy25CSPUrtqKQGNHflmX5 VWWokseHqtI6gT4/7yAvsC9PwS6F5sPY4Ysy/t6vqVbwW4GZ+9We+M6brfbxKN3X66IP 8eGDviyigKi+VEYEw3SfmYoEdPIWNyQh9CvXeZO7Q/EPcSPN0Ljt/PfrCbWfW3PJkifX 8chg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=Zel8JheyIoG3k864q8wwomvzSDmZrZiRTNXmm5oiNjc=; b=yfFAifCPsENC26cjRDEkiVDxByBImKmGikovp6oqcKvGzTMpWWCGyIWB4xPQuwlUH8 xxE0BqOhJx9NeTSW1n293u2LrZDTPo76a+1Yln7a88q+FxsxuexcVZXESup5FHFfRiWC CDDf9v1IvVeN03vOU9jLueA3nladxPGd7JTOyf5nH3Dr04IYqo3bqtDzxkDhUsQ2Bn58 l9hYSbUK4B6PphozpINaf0WZzes5b9ZqPzsiqgcpxOrf/Rc9w/ozkPuuMznLBpHBxT3h MnO99jX+79xwlDp6KBK3e5I8NSNk1nEV8p6TQbYMe5xSfxJM9fbYPMHw7Fty48BZn/Mz MFCA== 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 c18si3468875plo.251.2019.09.05.17.15.16; Thu, 05 Sep 2019 17:15:33 -0700 (PDT) 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 S2389911AbfIEQrG (ORCPT + 99 others); Thu, 5 Sep 2019 12:47:06 -0400 Received: from zeniv.linux.org.uk ([195.92.253.2]:38338 "EHLO ZenIV.linux.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2389741AbfIEQrF (ORCPT ); Thu, 5 Sep 2019 12:47:05 -0400 Received: from viro by ZenIV.linux.org.uk with local (Exim 4.92.1 #3 (Red Hat Linux)) id 1i5uuR-0002Cj-Kq; Thu, 05 Sep 2019 16:47:00 +0000 Date: Thu, 5 Sep 2019 17:46:59 +0100 From: Al Viro To: Naresh Kamboju Cc: Christoph Hellwig , Qian Cai , linux-fsdevel@vger.kernel.org, LKML , Linus Torvalds Subject: Re: "fs/namei.c: keep track of nd->root refcount status" causes boot panic Message-ID: <20190905164659.GO1131@ZenIV.linux.org.uk> References: <7C6CCE98-1E22-433C-BF70-A3CBCDED4635@lca.pw> <20190903123719.GF1131@ZenIV.linux.org.uk> <20190903130456.GA9567@infradead.org> <20190903134832.GH1131@ZenIV.linux.org.uk> <20190903135024.GA8274@infradead.org> <20190903135354.GI1131@ZenIV.linux.org.uk> <20190903153930.GA2791@infradead.org> <20190903175610.GM1131@ZenIV.linux.org.uk> <20190904123940.GA24520@infradead.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.12.0 (2019-05-25) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Sep 05, 2019 at 02:43:12PM +0530, Naresh Kamboju wrote: > Hi Christoph and Al Viro, > > Linux next 20190904 boot PASS now. > May i know which patch fixed this problem ? commit 84a2bd39405ffd5fa6d6d77e408c5b9210da98de Author: Al Viro Date: Tue Jul 16 21:20:17 2019 -0400 fs/namei.c: keep track of nd->root refcount status And I'm not going to abstain from folding the trivial fix (LOOKUP_ROOT_GRABBED had been given the same value as LOOKUP_EMPTY) into the commit. Sorry. I don't know how to tell CI systems out there about cases like that ("earlier version of this commit used to have a bug, fix folded in"). Something like Supersedes: might or might not be useful for tracking; not sure.