[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAA70yB5y1uLvtvEFLsE2C_ALLvSqEZ6XKA=zoPeSaH_eSAVL4w@mail.gmail.com>
Date: Fri, 22 Dec 2017 21:20:10 +0800
From: weiping zhang <zwp10758@...il.com>
To: Bruno Wolff III <bruno@...ff.to>
Cc: Jens Axboe <axboe@...nel.dk>, Laura Abbott <labbott@...hat.com>,
Jan Kara <jack@...e.cz>, linux-mm@...ck.org,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
regressions@...mhuis.info,
weiping zhang <zhangweiping@...ichuxing.com>,
linux-block@...r.kernel.org
Subject: Re: Regression with a0747a859ef6 ("bdi: add error handle for bdi_debug_register")
2017-12-22 12:53 GMT+08:00 Bruno Wolff III <bruno@...ff.to>:
> On Thu, Dec 21, 2017 at 17:16:03 -0600,
> Bruno Wolff III <bruno@...ff.to> wrote:
>>
>>
>> Enforcing mode alone isn't enough as I tested that one one machine at home
>> and it didn't trigger the problem. I'll try another machine late tonight.
>
>
> I got the problem to occur on my i686 machine when booting in enforcing
> mode. This machine uses raid 1 vua mdraid which may or may not be a factor
> in this problem. The boot log has a trace at the end and might be helpful,
> so I'm attaching it here.
Hi Bruno,
I can reproduce this issue in my QEMU test VM easily, just add an soft
RAID1, always trigger
that warning, I'll debug it later.
Powered by blists - more mailing lists