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:   Fri, 03 Jul 2020 19:19:22 -0700
To:     antlists <>,
        Christoph Hellwig <>,
CC:     Song Liu <>, Al Viro <>,
        Linus Torvalds <>,,
Subject: Re: [PATCH 09/16] initrd: remove the BLKFLSBUF call in handle_initrd

On July 3, 2020 5:18:48 PM PDT, antlists <> wrote:
>On 03/07/2020 04:40, H. Peter Anvin wrote:
>> On 2020-06-15 05:53, Christoph Hellwig wrote:
>>> BLKFLSBUF used to be overloaded for the ramdisk driver to free the
>>> ramdisk, which was completely different behavior compared to all
>>> drivers.  But this magic overload got removed in commit ff26956875c2
>>> ("brd: remove support for BLKFLSBUF"), so this call is entirely
>>> pointless now.
>>> Signed-off-by: Christoph Hellwig <>
>> Does *anyone* use initrd as opposed to initramfs anymore? It would
>> like a good candidate for deprecation/removal.
>Reading the gentoo mailing list, it seems there's a fair few people who
>don't use initramfs. I get the impression they don't use initrd either,
>I don't know too much about booting without an initramfs - I switched 
>ages ago - so what is possible and what they're actually doing, I don't

Not using any init userspace at all is an entirely different issue.
Sent from my Android device with K-9 Mail. Please excuse my brevity.

Powered by blists - more mailing lists