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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Wed, 6 Jul 2022 10:09:12 +0200
From:   Christoph Hellwig <hch@....de>
To:     Bagas Sanjaya <bagasdotme@...il.com>
Cc:     linux-block@...r.kernel.org, Christoph Hellwig <hch@....de>,
        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 09:53:36AM +0700, Bagas Sanjaya wrote:
> Hi,
> 
> I first noticed this issue on v5.18.9, and still found on v5.19-rc5.
> 
> Looking at dmesg, I see error message on loop8 device:
> 
> [   41.319699] Dev loop8: unable to read RDB block 8
> [   41.320566]  loop8: unable to read partition table
> [   41.320597] loop8: partition table beyond EOD, truncated
> 
> My Debian 11 laptop is also run LXD (as development server).
> 
> 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.