linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: weiping zhang <zwp10758@gmail.com>
To: Bruno Wolff III <bruno@wolff.to>
Cc: Laura Abbott <labbott@redhat.com>, Jan Kara <jack@suse.cz>,
	Jens Axboe <axboe@kernel.dk>,
	linux-mm@kvack.org,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	regressions@leemhuis.info, linux-block@vger.kernel.org
Subject: Re: Regression with a0747a859ef6 ("bdi: add error handle for bdi_debug_register")
Date: Sun, 17 Dec 2017 21:43:50 +0800	[thread overview]
Message-ID: <CAA70yB7wL_Wq5S8XQ9zHuLPDdwepv7dYdKALL8Sg0q6CNdAz5g@mail.gmail.com> (raw)
In-Reply-To: <20171216163226.GA1796@wolff.to>

2017-12-17 0:32 GMT+08:00 Bruno Wolff III <bruno@wolff.to>:
> On Fri, Dec 15, 2017 at 13:51:22 -0600,
>  Bruno Wolff III <bruno@wolff.to> 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: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2017-12-17 13:43 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-14  0:54 Regression with a0747a859ef6 ("bdi: add error handle for bdi_debug_register") Laura Abbott
2017-12-14  8:24 ` Bruno Wolff III
2017-12-14 10:09   ` weiping zhang
2017-12-14 10:29     ` Bruno Wolff III
2017-12-14 15:41     ` Bruno Wolff III
2017-12-15  1:22       ` weiping zhang
2017-12-15  1:44         ` Bruno Wolff III
2017-12-15  2:04           ` weiping zhang
2017-12-15  2:11             ` Bruno Wolff III
2017-12-15 11:10             ` Bruno Wolff III
2017-12-15 14:02               ` weiping zhang
2017-12-15 16:30                 ` Bruno Wolff III
2017-12-15 17:18                   ` Laura Abbott
2017-12-15 17:40                     ` Bruno Wolff III
2017-12-15 19:51                 ` Bruno Wolff III
2017-12-16 16:32                   ` Bruno Wolff III
2017-12-17 13:43                     ` weiping zhang [this message]
2017-12-17 15:54                       ` Bruno Wolff III
2017-12-18 21:53                       ` Bruno Wolff III
2017-12-19 16:17                       ` Bruno Wolff III
2017-12-19 18:24                         ` Shaohua Li
2017-12-19 19:48                           ` Bruno Wolff III
2017-12-20  0:20                           ` Bruno Wolff III
2017-12-21 13:00 ` Bruno Wolff III
2017-12-21 14:01   ` weiping zhang
2017-12-21 15:18     ` Bruno Wolff III
2017-12-21 15:31       ` weiping zhang
2017-12-21 15:36         ` Bruno Wolff III
2017-12-21 15:48           ` weiping zhang
2017-12-21 16:42             ` Bruno Wolff III
2017-12-21 17:02               ` Jens Axboe
2017-12-21 17:46                 ` weiping zhang
2017-12-21 18:15                 ` Bruno Wolff III
2017-12-21 23:16                   ` Bruno Wolff III
2017-12-22  4:53                     ` Bruno Wolff III
2017-12-22 13:20                       ` weiping zhang
2017-12-22 14:04                         ` Bruno Wolff III
2017-12-29 16:30                           ` weiping zhang
2017-12-29 18:44                             ` Bruno Wolff III
2017-12-29 16:36                           ` weiping zhang
2017-12-22  0:29                 ` James Bottomley
2017-12-22  1:29                   ` weiping zhang

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAA70yB7wL_Wq5S8XQ9zHuLPDdwepv7dYdKALL8Sg0q6CNdAz5g@mail.gmail.com \
    --to=zwp10758@gmail.com \
    --cc=axboe@kernel.dk \
    --cc=bruno@wolff.to \
    --cc=jack@suse.cz \
    --cc=labbott@redhat.com \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=regressions@leemhuis.info \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).