From: Arjan van de Ven <arjan@linux.intel.com>
To: Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>,
Alexander Viro <viro@zeniv.linux.org.uk>
Cc: Jens Axboe <axboe@kernel.dk>,
linux-block@vger.kernel.org, Petr Vorel <pvorel@suse.cz>,
Pavel Tatashin <pasha.tatashin@soleen.com>,
Tyler Hicks <tyhicks@linux.microsoft.com>,
Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH] loop: reintroduce global lock for safe loop_validate_file() traversal
Date: Tue, 6 Jul 2021 07:35:59 -0700 [thread overview]
Message-ID: <fdd3e7bb-4ab6-2a37-a03a-56e088b32db3@linux.intel.com> (raw)
In-Reply-To: <258f1892-bbbe-67e2-ead9-3287a3d7578b@i-love.sakura.ne.jp>
On 7/3/2021 10:42 PM, Tetsuo Handa wrote:
>
> It is not clear why the size of old and new image files need to be the same.
filesystems have a heck of a time dealing with suddenly a smaller disk ;)
note that the commit in question predates the ability for filesystems to grow into larger spaces
or most of hotplug.
so it's quite possible that today we can allow switching to a larger file just fine
prev parent reply other threads:[~2021-07-06 14:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-02 15:30 [PATCH] loop: reintroduce global lock for safe loop_validate_file() traversal Tetsuo Handa
2021-07-02 17:28 ` Tetsuo Handa
2021-07-06 5:46 ` Christoph Hellwig
2021-07-06 11:19 ` [PATCH v2] " Tetsuo Handa
2021-07-06 14:40 ` [PATCH v3] " Tetsuo Handa
2021-07-19 13:34 ` Tetsuo Handa
2021-07-23 16:19 ` Jens Axboe
2021-07-24 6:57 ` Christoph Hellwig
2021-07-04 5:42 ` [PATCH] " Tetsuo Handa
2021-07-06 5:43 ` Christoph Hellwig
2021-07-06 14:35 ` Arjan van de Ven [this message]
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=fdd3e7bb-4ab6-2a37-a03a-56e088b32db3@linux.intel.com \
--to=arjan@linux.intel.com \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=linux-block@vger.kernel.org \
--cc=pasha.tatashin@soleen.com \
--cc=penguin-kernel@i-love.sakura.ne.jp \
--cc=pvorel@suse.cz \
--cc=tyhicks@linux.microsoft.com \
--cc=viro@zeniv.linux.org.uk \
/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;
as well as URLs for NNTP newsgroup(s).