linux-kernel - Re: unable to read RDB block due to b9684a71fca793

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: <aa126250-9f7f-b48b-79dc-bdb8b4bf5ca9@gmail.com>
Date:   Wed, 6 Jul 2022 17:16:06 +0700
From:   Bagas Sanjaya <bagasdotme@...il.com>
To:     Christoph Hellwig <hch@....de>
Cc:     linux-block@...r.kernel.org, Ming Lei <ming.lei@...hat.com>,
        Jens Axboe <axboe@...nel.dk>, linux-kernel@...r.kernel.org
Subject: Re: unable to read RDB block due to b9684a71fca793

On 7/6/22 15:09, Christoph Hellwig wrote:
>> Bisecting between v5.18 and v5.19-rc5, the culprit is commit b9684a71fca793
>> ("block, loop: support partitions without scanning").
> 
> Which just restores the previous behavior of optionally allowing to
> scan for partitions on all loop devices.  So that error had been
> there before and just disappeared due to a regression.

OK.

Can partition scanning for loop devices be disabled? If so, how?

-- 
An old man doll... just what I always wanted! - Clara