linux-block.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael Tretter <m.tretter@pengutronix.de>
To: linux-block@vger.kernel.org
Cc: Josef Bacik <jbacik@fb.com>, kernel@pengutronix.de, axboe@kernel.dk
Subject: Re: [PATCH] nbd: do not update block size if file system is mounted
Date: Thu, 15 Mar 2018 11:00:57 +0100	[thread overview]
Message-ID: <20180315110057.13eecda6@litschi.hi.pengutronix.de> (raw)
In-Reply-To: <20180228095456.31472-1-m.tretter@pengutronix.de>

On Wed, 28 Feb 2018 10:54:56 +0100, Michael Tretter wrote:
> If a file system is mounted on the nbd during a disconnect, resetting
> the size to 0, might change the block size and destroy the buffer_head
> mappings. This will cause a infinite loop when the file system looks for
> the buffer_heads for flushing.
> 
> Only set the file size to 0, if we are the only opener of the nbd.
> 
> Signed-off-by: Michael Tretter <m.tretter@pengutronix.de>
> ---
>  drivers/block/nbd.c | 3 ++-
>  1 file changed, 2 insertions(+), 1 deletion(-)
> 
> diff --git a/drivers/block/nbd.c b/drivers/block/nbd.c
> index 5f2a4240a204..0d1dbb60430b 100644
> --- a/drivers/block/nbd.c
> +++ b/drivers/block/nbd.c
> @@ -1118,7 +1118,8 @@ static int nbd_start_device_ioctl(struct nbd_device *nbd, struct block_device *b
>  	if (ret)
>  		sock_shutdown(nbd);
>  	mutex_lock(&nbd->config_lock);
> -	bd_set_size(bdev, 0);
> +	if (bdev->bd_openers <= 1)
> +		bd_set_size(bdev, 0);
>  	/* user requested, ignore socket errors */
>  	if (test_bit(NBD_DISCONNECT_REQUESTED, &config->runtime_flags))
>  		ret = 0;

Are there any comments on this patch?

Michael

  reply	other threads:[~2018-03-15 10:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-28  9:54 [PATCH] nbd: do not update block size if file system is mounted Michael Tretter
2018-03-15 10:00 ` Michael Tretter [this message]
2018-03-16 16:36   ` Jens Axboe
2018-04-13 14:25     ` Michael Tretter
2018-04-14  1:10       ` Josef Bacik
2018-04-17  9:15         ` Michael Tretter
2018-05-15  8:44           ` Michael Tretter

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=20180315110057.13eecda6@litschi.hi.pengutronix.de \
    --to=m.tretter@pengutronix.de \
    --cc=axboe@kernel.dk \
    --cc=jbacik@fb.com \
    --cc=kernel@pengutronix.de \
    --cc=linux-block@vger.kernel.org \
    /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).