From: Jens Axboe <axboe@kernel.dk>
To: Jan Kara <jack@suse.cz>
Cc: linux-block@vger.kernel.org, Josef Bacik <jbacik@fb.com>,
Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
Subject: Re: [PATCH 0/2] blkdev: Fix livelock when loop device updates capacity
Date: Tue, 15 Jan 2019 07:31:22 -0700 [thread overview]
Message-ID: <81413910-c4ce-6380-e989-94de0d11ce2e@kernel.dk> (raw)
In-Reply-To: <20190114084811.14455-1-jack@suse.cz>
On 1/14/19 1:48 AM, Jan Kara wrote:
> Hello,
>
> this series fixes a long standing issue with loop device which can change block
> device size under a mounted filesystem which causes infinite loop inside buffer
> head code. See patch 2/2 for details about the problem.
>
> Note that generally it is dangerous to resize the loop device when filesystem
> is mounted on top of it. However there are some valid use cases for this (such
> as growing the loop device and then increasing the filesystem size) so we
> cannot just restrict the functionality to exclusive owners of the device.
That's really a shame...
Anyway, applied for 5.0, thanks Jan.
--
Jens Axboe
prev parent reply other threads:[~2019-01-15 14:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-14 8:48 [PATCH 0/2] blkdev: Fix livelock when loop device updates capacity Jan Kara
2019-01-14 8:48 ` [PATCH 1/2] nbd: Use set_blocksize() to set device blocksize Jan Kara
2019-01-14 8:48 ` [PATCH 2/2] blockdev: Fix livelocks on loop device Jan Kara
2019-01-14 8:48 ` [PATCH] loop: Add test for changing capacity when filesystem is mounted Jan Kara
[not found] ` <f3988910-5c64-2ab4-a4e8-8255d72458b1@i-love.sakura.ne.jp>
[not found] ` <20190114104119.GE13316@quack2.suse.cz>
2019-01-14 10:50 ` Jan Kara
2019-01-14 19:10 ` Chaitanya Kulkarni
2019-01-15 7:39 ` Jan Kara
2019-01-15 14:31 ` Jens Axboe [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=81413910-c4ce-6380-e989-94de0d11ce2e@kernel.dk \
--to=axboe@kernel.dk \
--cc=jack@suse.cz \
--cc=jbacik@fb.com \
--cc=linux-block@vger.kernel.org \
--cc=penguin-kernel@I-love.SAKURA.ne.jp \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.