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 09:36:31 -0600
From:   Bruno Wolff III <>
To:     weiping zhang <>
Cc:     Laura Abbott <>, Jan Kara <>,
        Jens Axboe <>,,
        Linux Kernel Mailing List <>,,
        weiping zhang <>,
Subject: Re: Regression with a0747a859ef6 ("bdi: add error handle for

On Thu, Dec 21, 2017 at 23:31:40 +0800,
  weiping zhang <> wrote:
>does every time boot fail can trigger WANRING in device_add_disk ?

Not that I see. But the message could scroll off the screen. The boot gets 
far enough that systemd copies over dmesg output to permanent storage that 
I can see on my next successful boot. That's where I looked for the warning 
output you want. I never saw it for any kernels I compiled myself. Only 
when I test kernels built by Fedora do I see it.

I just tried booting to single user and the boot still hangs.

When I build the kernels, the compiler options are probably a bit different 
than when Fedora does. That might affect what happens during boot.

Powered by blists - more mailing lists