Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757334AbdLQNny (ORCPT ); Sun, 17 Dec 2017 08:43:54 -0500 Received: from mail-wm0-f53.google.com ([74.125.82.53]:46249 "EHLO mail-wm0-f53.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752118AbdLQNnw (ORCPT ); Sun, 17 Dec 2017 08:43:52 -0500 X-Google-Smtp-Source: ACJfBouXuok/SzAS+dKEodYQ520yau28p56wtOLHn5jRC7SdRewO6+Swt4WAIIu8gGxAUNsVA/+Gp++UXCWnUlSEpoQ= 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" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 921 Lines: 20 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.