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] [day] [month] [year] [list]

Date:   Wed, 6 Jul 2022 14:00:10 +0200
From:   Christoph Hellwig <hch@....de>
To:     Bagas Sanjaya <bagasdotme@...il.com>
Cc:     Christoph Hellwig <hch@....de>, 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 Wed, Jul 06, 2022 at 05:16:06PM +0700, Bagas Sanjaya wrote:
> 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?

It is disabled by default.  But some tools force partitions rescans,
which is what that commit enabled.  parted was the original reproducer.