Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756851AbdLOQeK (ORCPT ); Fri, 15 Dec 2017 11:34:10 -0500 Received: from wolff.to ([98.103.208.27]:35250 "HELO wolff.to" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with SMTP id S1756832AbdLOQeG (ORCPT ); Fri, 15 Dec 2017 11:34:06 -0500 Date: Fri, 15 Dec 2017 10:30:48 -0600 From: Bruno Wolff III To: weiping zhang Cc: Laura Abbott , Jan Kara , Jens Axboe , linux-mm@kvack.org, Linux Kernel Mailing List , regressions@leemhuis.info, linux-block@vger.kernel.org Subject: Re: Regression with a0747a859ef6 ("bdi: add error handle for bdi_debug_register") Message-ID: <20171215163048.GA15928@wolff.to> References: <20171214082452.GA16698@wolff.to> <20171214100927.GA26167@localhost.didichuxing.com> <20171214154136.GA12936@wolff.to> <20171215014417.GA17757@wolff.to> <20171215111050.GA30737@wolff.to> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.9.1 (2017-09-22) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 997 Lines: 18 On Fri, Dec 15, 2017 at 22:02:20 +0800, weiping zhang wrote: > >Yes, please help reproduce this issue include my debug patch. Reproduce means >we can see WARN_ON in device_add_disk caused by failure of bdi_register_owner. I'm not sure why yet, but I'm only getting the warning message you want with Fedora kernels, not the ones I am building (with or without your test patch). I'll attach a debug config file if you want to look there. But in theory that should be essentially what Fedora is using for theirs. They probably have some out of tree patches they are applying, but I wouldn't expect those to make a difference here. I think they now have a tree somewhere that I can try to build from that has their patches applied to the upstream kernel and if I can find it I will try building it just to test this out. I only have about 6 hours of physical access to the machine exhibiting the problem, and after that I won't be able to do test boots until Monday.