Received: by 2002:a25:c593:0:0:0:0:0 with SMTP id v141csp2535310ybe; Tue, 3 Sep 2019 14:32:00 -0700 (PDT) X-Google-Smtp-Source: APXvYqzHNXMKTyvm0eM3KPvgyI28lhZf58FSBOm5yFiHPAP/YdwdyS58CoTGhEs+sVqErGM5nf2Y X-Received: by 2002:a17:90a:734a:: with SMTP id j10mr1411025pjs.63.1567546320238; Tue, 03 Sep 2019 14:32:00 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1567546320; cv=none; d=google.com; s=arc-20160816; b=Q0nhsL7k5C9D1OHVzb1v3cg7vHj/BGG8qvMBkX17UVeYMOZTzXYrQvfmcOBedECwQH i03PNTlXy6kKR7wPBSYNSTjnp943m52vHfi+IPxSs7i7quQMmc/eiGo/KMcAq+e4tLjA OCAD5WVEe87W9iaPvj4fzh99SJJqgykauNMMm2sSKE5ClVg655eZDj0qqJkgNf7PvaNR bLl0AveKeCBOtD/u9lV5dwyf+HuNpOQJxjIcihelk1xfhEgxMkXsSNVGqNJSFqGvSjw0 heEl9ZkdZdQkl54bQgaGD58Gk+mTT2XCLC7gfHU99RF/zYeGbpueB7TTDbn2afak4p57 opnA== 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=jrvTrZw+GFAYGhgBETGlmDR6jUBbLjuLKmw5rT+W26c=; b=PUGlD06Ke2LfrvkUdsaYQEitt8++he4eVRztS9JkGGSycFNz6ufCfCdM2OzFQLj6XN XfVqJvkpfyCPZh5VOwBOeodpjTXg81D5/t6T33I2+Ej/hTP/Dj+5NRd35Z7KDaXZprI3 GpWJmAzvZ660TPbWoadOB5P3bomtAppVLILZnxi9/pbNoPzvAtHlD2mLX7OnnEOyjmyr cUcdlEBOXVwehP/jU/wz8K1yUM9mJi3uoGJ6VcxkpTjb47QchZIKH3fnUIRk7WVog3DM ZkBwVKFu5YrV+zpbfz+5wBQwh+RM3IoocUN3gtGq5XFo7/iLZkfqK66tQE2iVcuovzMP l2yQ== 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 c9si1063306pjr.0.2019.09.03.14.31.44; Tue, 03 Sep 2019 14:32:00 -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 S1726853AbfICVaq (ORCPT + 99 others); Tue, 3 Sep 2019 17:30:46 -0400 Received: from outgoing-auth-1.mit.edu ([18.9.28.11]:47681 "EHLO outgoing.mit.edu" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1726179AbfICVaq (ORCPT ); Tue, 3 Sep 2019 17:30:46 -0400 Received: from callcc.thunk.org (guestnat-104-133-0-96.corp.google.com [104.133.0.96] (may be forged)) (authenticated bits=0) (User authenticated as tytso@ATHENA.MIT.EDU) by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id x83LUUn0009589 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Tue, 3 Sep 2019 17:30:32 -0400 Received: by callcc.thunk.org (Postfix, from userid 15806) id 3341E42049E; Tue, 3 Sep 2019 17:30:30 -0400 (EDT) Date: Tue, 3 Sep 2019 17:30:30 -0400 From: "Theodore Y. Ts'o" To: Christoph Hellwig Cc: Al Viro , Qian Cai , linux-fsdevel@vger.kernel.org, LKML Subject: Re: "fs/namei.c: keep track of nd->root refcount status" causes boot panic Message-ID: <20190903213030.GE2899@mit.edu> 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> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190903135024.GA8274@infradead.org> User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Sep 03, 2019 at 06:50:24AM -0700, Christoph Hellwig wrote: > On Tue, Sep 03, 2019 at 02:48:32PM +0100, Al Viro wrote: > > Not sure what would be the best way to do it... I don't mind breaking > > the out-of-tree modules, whatever their license is; what I would rather > > avoid is _quiet_ breaking of such. > > Any out of tree module running against an upstream kernel will need > a recompile for a new version anyway. So I would not worry about it > at all. I'm really confused. What out-of-tree module are people needing to use when doing linux-next testing? That seems like a recipe for disaster... - Ted