[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <2D8954BF-E3D2-4A61-AAE2-A3FDD080C26A@suse.com>
Date: Thu, 8 Jun 2017 08:45:31 +0800
From: James Wang <jnwang@...e.com>
To: Christoph Hellwig <hch@...radead.org>
Cc: axboe@...com, hare@...e.com, linux-block@...r.kernel.org,
linux-kernel@...r.kernel.org, mgorman@...e.com
Subject: Re: [PATCH] Fix loop device flush before configure
Ok I got it blktests is a suite. I'd like to contribute something. If you need, we adapt you,;-)!
But I have to learn some how to do that, need time.
James
>From subway.
在 2017年6月7日,21:17,Christoph Hellwig <hch@...radead.org> 写道:
>> Testing steps are following:
>> modprobe loop max_loop=64
>> dd if=/dev/zero of=disk bs=512 count=200K
>> for((i=0;i<4;i++))do losetup -f disk; done
>> mkfs.ext4 -F /dev/loop0
>> for((i=0;i<4;i++))do mkdir t$i; mount /dev/loop$i t$i;done
>> for f in `ls /dev/loop[0-9]*|sort`; do \
>> echo $f; dd if=$f of=/dev/null bs=512 count=1; \
>> done
>
> Can you write this up for blktests, please?
>
Powered by blists - more mailing lists