From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: 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 In-Reply-To: List-ID: 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. From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-it0-f72.google.com (mail-it0-f72.google.com [209.85.214.72]) by kanga.kvack.org (Postfix) with ESMTP id 13B686B026C for ; Tue, 19 Dec 2017 11:21:38 -0500 (EST) Received: by mail-it0-f72.google.com with SMTP id b11so2462683itj.0 for ; Tue, 19 Dec 2017 08:21:38 -0800 (PST) Received: from wolff.to (wolff.to. [98.103.208.27]) by mx.google.com with SMTP id v81si4571674ioi.128.2017.12.19.08.21.36 for ; Tue, 19 Dec 2017 08:21:37 -0800 (PST) Date: Tue, 19 Dec 2017 10:17:43 -0600 From: Bruno Wolff III 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: Sender: owner-linux-mm@kvack.org List-ID: 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 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. -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: email@kvack.org