From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Christoph Hellwig <hch@lst.de>
Cc: linux-block@vger.kernel.org, Ming Lei <ming.lei@redhat.com>,
Jens Axboe <axboe@kernel.dk>,
linux-kernel@vger.kernel.org
Subject: Re: unable to read RDB block due to b9684a71fca793
Date: Wed, 6 Jul 2022 17:16:06 +0700 [thread overview]
Message-ID: <aa126250-9f7f-b48b-79dc-bdb8b4bf5ca9@gmail.com> (raw)
In-Reply-To: <20220706080912.GA32273@lst.de>
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
next prev parent reply other threads:[~2022-07-06 10:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-06 2:53 unable to read RDB block due to b9684a71fca793 Bagas Sanjaya
2022-07-06 8:09 ` Christoph Hellwig
2022-07-06 10:16 ` Bagas Sanjaya [this message]
2022-07-06 12:00 ` Christoph Hellwig
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=aa126250-9f7f-b48b-79dc-bdb8b4bf5ca9@gmail.com \
--to=bagasdotme@gmail.com \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ming.lei@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox