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  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]
Date:   Thu, 21 Dec 2017 23:31:40 +0800
From:   weiping zhang <>
To:     Bruno Wolff III <>
Cc:     Laura Abbott <>, Jan Kara <>,
        Jens Axboe <>,,
        Linux Kernel Mailing List <>,,
        weiping zhang <>,
Subject: Re: Regression with a0747a859ef6 ("bdi: add error handle for bdi_debug_register")

2017-12-21 23:18 GMT+08:00 Bruno Wolff III <>:
> On Thu, Dec 21, 2017 at 22:01:33 +0800,
>  weiping zhang <> wrote:
>> Hi,
>> how do you do bisect ?build all kernel commit one by one ?
>> as you did before:
> I just did the one bisect using Linus' tree. After each build, I would do a
> test boot and see if the boot was normal or if I got errors and an eventual
> hang before boot.
> Since then I have used git revert to revert just the problem commit from
> later kernels (such as v4.15-rc4) and when I do the system boots normally.
> And when I don't do the revert or just use stock Fedora kernels the problem
> occurs every time.
does every time boot fail can trigger WANRING in device_add_disk ?

Powered by blists - more mailing lists