linux-kernel - Re: Regression with a0747a859ef6 ("bdi: add error handle for bdi_debug

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20171222140423.GA23107@wolff.to>
Date:   Fri, 22 Dec 2017 08:04:23 -0600
From:   Bruno Wolff III <bruno@...ff.to>
To:     weiping zhang <zwp10758@...il.com>
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")

On Fri, Dec 22, 2017 at 21:20:10 +0800,
  weiping zhang <zwp10758@...il.com> wrote:
>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.

Great. When you have a fix, I can test it.