Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751969AbdLSQ2U (ORCPT ); Tue, 19 Dec 2017 11:28:20 -0500 Received: from wolff.to ([98.103.208.27]:37556 "HELO wolff.to" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with SMTP id S1751670AbdLSQ2S (ORCPT ); Tue, 19 Dec 2017 11:28:18 -0500 Date: Tue, 19 Dec 2017 10:17:43 -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: <20171219161743.GA6960@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: 635 Lines: 11 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. The problem is still in rc4. Reverting the commit still fixes the problem. I tested that warning level messages should appear using lkdtm. While there could be something weird relating to the WARN_ON macro, more likely there is something different about the boots with the kernels I build (the exact way initramfs is built is probably different) and probably that (WARN_ON) code is not getting executed.