Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Date:   Thu, 10 Jun 2021 22:45:30 +0800
From:   Ming Lei <ming.lei@redhat.com>
To:     Ingo Franzki <ifranzki@linux.ibm.com>
Cc:     Jens Axboe <axboe@kernel.dk>, linux-block@vger.kernel.org,
        linux-kernel@vger.kernel.org,
        Juergen Christ <jchrist@linux.ibm.com>
Subject: Re: loop_set_block_size: loop0 () has still dirty pages (nrpages=2)
Message-ID: <YMIliuPi2tTLUJxv@T590>
References: <8bed44f2-273c-856e-0018-69f127ea4258@linux.ibm.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <8bed44f2-273c-856e-0018-69f127ea4258@linux.ibm.com>
Precedence: bulk

On Tue, Jun 08, 2021 at 02:01:29PM +0200, Ingo Franzki wrote:
> Hi all,
> 
> we occasionally encounter a problem when setting up a loop device in one of our automated testcases.
> 
> We set up a loop device as follows:
> 
>     # dd if=/dev/zero of=/var/tmp/loopbackfile1.img bs=1M count=2500 status=none
>     # losetup --sector-size 4096 -fP --show /var/tmp/loopbackfile1.img
> 
> This works fine most of the times, but in the seldom case of the error, we get 'losetup: /var/tmp/loopbackfile1.img: failed to set up loop device: Resource temporarily unavailable'.
> 
> I am sure that no other loop device is currently defined, so we don't run out of loop devices.
> 
> We also see the following message in the syslog when the error occurs:
> 
>      loop_set_block_size: loop0 () has still dirty pages (nrpages=2)
> 
> The nrpages number varies from time to time. 
> 
> "Resource temporarily unavailable" is EAGAIN, and function loop_set_block_size() in drivers/block/loop.c returns this after printing the syslog message via pr_warn:
> 
> static int loop_set_block_size(struct loop_device *lo, unsigned long arg)
> {
> 	int err = 0;
> 
> 	if (lo->lo_state != Lo_bound)
> 		return -ENXIO;
> 
> 	err = loop_validate_block_size(arg);
> 	if (err)
> 		return err;
> 
> 	if (lo->lo_queue->limits.logical_block_size == arg)
> 		return 0;
> 
> 	sync_blockdev(lo->lo_device);
> 	invalidate_bdev(lo->lo_device);
> 
> 	blk_mq_freeze_queue(lo->lo_queue);
> 
> 	/* invalidate_bdev should have truncated all the pages */
> 	if (lo->lo_device->bd_inode->i_mapping->nrpages) {
> 		err = -EAGAIN;
> 		pr_warn("%s: loop%d (%s) has still dirty pages (nrpages=%lu)\n",
> 			__func__, lo->lo_number, lo->lo_file_name,
> 			lo->lo_device->bd_inode->i_mapping->nrpages);
> 		goto out_unfreeze;
> 	}
> 
> 	blk_queue_logical_block_size(lo->lo_queue, arg);
> 	blk_queue_physical_block_size(lo->lo_queue, arg);
> 	blk_queue_io_min(lo->lo_queue, arg);
> 	loop_update_dio(lo);
> out_unfreeze:
> 	blk_mq_unfreeze_queue(lo->lo_queue);
> 
> 	return err;
> }
> 
> So looks like invalidate_bdev() did actually not truncate all the pages under some circumstances....
> 
> The problem only happens when '--sector-size 4096' is specified, with the default sector size is always works. It does not call loop_set_block_size() in the default case I guess.
> 
> The loop0 device has certainly be used by other testcases before, most likely with the default block size. But at the time of this run, no loop device is currently active (losetup shows nothing). 
> 
> Anyone have an idea what goes wrong here? 

It returns '-EAGAIN' to ask userspace to try again.

I understand loop_set_block_size() doesn't prevent page cache of this
loop disk from being dirtied, so it isn't strange to
see lo_device->bd_inode->i_mapping->nrpages isn't zero after sync_blockdev()
& invalidate_bdev() on loop.

> 
> This happens on upstream kernels on the s390x platform, but I can't tell if is related to the platform or a specific kernel version. 

It can be reproduced easily when you run buffered write on loop disk,
meantime keeping to change block size from one to another on this loop.


Thanks,
Ming