From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: MIME-Version: 1.0 In-Reply-To: <20171216163226.GA1796@wolff.to> References: <20171214082452.GA16698@wolff.to> <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> From: weiping zhang Date: Sun, 17 Dec 2017 21:43:50 +0800 Message-ID: Subject: Re: Regression with a0747a859ef6 ("bdi: add error handle for bdi_debug_register") To: Bruno Wolff III Cc: Laura Abbott , Jan Kara , Jens Axboe , linux-mm@kvack.org, Linux Kernel Mailing List , regressions@leemhuis.info, linux-block@vger.kernel.org Content-Type: text/plain; charset="UTF-8" List-ID: 2017-12-17 0:32 GMT+08:00 Bruno Wolff III : > On Fri, Dec 15, 2017 at 13:51:22 -0600, > Bruno Wolff III wrote: >> >> >> I do not know what is different. Do you have any ideas? Most likely I >> won't be able to test any more kernels until Monday (unless I can use most >> of my most recent build over again very soon). > > > The .config looks like it should be OK. I'll test setting loglevel on boot > in case the default is different than what the config file says. I can't do > that until Monday morning. > > I think it is more likely the the WARN_ON macro code isn't being compiled in > for some reason. I haven't confirmed that, nor have I found anything that > would leave that code out when I do a make, but include it during Fedora > builds. 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. From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wr0-f199.google.com (mail-wr0-f199.google.com [209.85.128.199]) by kanga.kvack.org (Postfix) with ESMTP id 993286B0033 for ; Sun, 17 Dec 2017 08:43:52 -0500 (EST) Received: by mail-wr0-f199.google.com with SMTP id z109so2143445wrb.19 for ; Sun, 17 Dec 2017 05:43:52 -0800 (PST) Received: from mail-sor-f41.google.com (mail-sor-f41.google.com. [209.85.220.41]) by mx.google.com with SMTPS id m13sor6703876edi.53.2017.12.17.05.43.50 for (Google Transport Security); Sun, 17 Dec 2017 05:43:51 -0800 (PST) MIME-Version: 1.0 In-Reply-To: <20171216163226.GA1796@wolff.to> References: <20171214082452.GA16698@wolff.to> <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> From: weiping zhang Date: Sun, 17 Dec 2017 21:43:50 +0800 Message-ID: Subject: Re: Regression with a0747a859ef6 ("bdi: add error handle for bdi_debug_register") Content-Type: text/plain; charset="UTF-8" Sender: owner-linux-mm@kvack.org List-ID: To: Bruno Wolff III Cc: Laura Abbott , Jan Kara , Jens Axboe , linux-mm@kvack.org, Linux Kernel Mailing List , regressions@leemhuis.info, linux-block@vger.kernel.org 2017-12-17 0:32 GMT+08:00 Bruno Wolff III : > On Fri, Dec 15, 2017 at 13:51:22 -0600, > Bruno Wolff III wrote: >> >> >> I do not know what is different. Do you have any ideas? Most likely I >> won't be able to test any more kernels until Monday (unless I can use most >> of my most recent build over again very soon). > > > The .config looks like it should be OK. I'll test setting loglevel on boot > in case the default is different than what the config file says. I can't do > that until Monday morning. > > I think it is more likely the the WARN_ON macro code isn't being compiled in > for some reason. I haven't confirmed that, nor have I found anything that > would leave that code out when I do a make, but include it during Fedora > builds. 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. -- 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