Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S965288AbdLRV5i (ORCPT ); Mon, 18 Dec 2017 16:57:38 -0500 Received: from wolff.to ([98.103.208.27]:36886 "HELO wolff.to" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with SMTP id S965215AbdLRV5h (ORCPT ); Mon, 18 Dec 2017 16:57:37 -0500 Date: Mon, 18 Dec 2017 15:53:51 -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: <20171218215351.GA24604@wolff.to> References: <20171214100927.GA26167@localhost.didichuxing.com> <20171214154136.GA12936@wolff.to> <20171215014417.GA17757@wolff.to> <20171215111050.GA30737@wolff.to> <20171215195122.GA27126@wolff.to> <20171216163226.GA1796@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: 679 Lines: 12 On Sun, Dec 17, 2017 at 21:43:50 +0800, weiping zhang wrote: >Hi, thanks for testing, I think you first reproduce this issue(got WARNING >at device_add_disk) by your own build, then add my debug patch. I'm going to try testing warnings with a kernel I've built, to try to determine if warnings are working at all for the ones I'm building. However it might be that the WARN_ONs are not being reached for the kernels I've built. If that turns out to be the case, I may not be able to get you both the output from the WARN_ONs and the output from your debugging patch at the same time. My next kernel build isn't going to finish in time to test today.