From: Xiao Yang <yangx.jy@cn.fujitsu.com>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH] lib/tst_device.c: Make sure all loop deivces fot test are detached
Date: Thu, 13 Sep 2018 12:17:23 +0800 [thread overview]
Message-ID: <5B99E4D3.7070408@cn.fujitsu.com> (raw)
In-Reply-To: <20180912123332.GC463@rei>
On 2018/09/12 20:33, Cyril Hrubis wrote:
> Hi!
>> Running statx05 by runltp without -b option every time attached a loop
>> device but didn't detach it, as below:
>> ------------------------------------------------------------------
>> ...
>> tst_device.c:230: INFO: Using test device LTP_DEV='/dev/loop0'
>> tst_device.c:268: INFO: Skipping $LTP_DEV size 256MB, requested size 512MB
>> tst_device.c:83: INFO: Found free device '/dev/loop1'
>> tst_mkfs.c:83: INFO: Formatting /dev/loop1 with ext4 opts='' extra opts='-O encrypt'
>> ...
>> NAME SIZELIMIT OFFSET AUTOCLEAR RO BACK-FILE DIO
>> /dev/loop1 0 0 0 0 /tmp/ltp-gsrcFAkGpZ/Wka3bp/test_dev.img (deleted) 0
>> ------------------------------------------------------------------
>>
>> runltp created a block device with default 256M size by attaching a free loop
>> device and set LTP_DEV variable, but statx05 needed a 512M block device, so
>> tst_acquire_device__() in setup skipped the $LTP_DEV device and created another
>> block device with 512M size by attaching another free loop device. Unfortunately,
>> tst_release_device() in cleanup cannot detach the 512M block device due to the
>> defined LTP_DEV.
> Btw his has been fixed for statx since:
>
> commit e583eacf3c9781116c19dec4c7e8c0aa4ed01ed5
> Author: Cyril Hrubis<chrubis@suse.cz>
> Date: Tue Sep 11 17:27:43 2018 +0200
>
> syscalls/statx05: Fix test on ppc64le
>
>
> But yes apart from that the test library is still broken.
>
>> We should just skip the detach in tst_release_device() when LTP_DEV variable is
>> set and device_acquired flag is not set.
>>
>> Signed-off-by: Xiao Yang<yangx.jy@cn.fujitsu.com>
>> ---
>> lib/tst_device.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/lib/tst_device.c b/lib/tst_device.c
>> index 463743443..23c99dba2 100644
>> --- a/lib/tst_device.c
>> +++ b/lib/tst_device.c
>> @@ -313,7 +313,7 @@ int tst_release_device(const char *dev)
>> {
>> int ret;
>>
>> - if (getenv("LTP_DEV"))
>> + if (getenv("LTP_DEV")&& !device_acquired)
>> return 0;
> I guess that this really should be just:
>
> if (!device_acquired)
> return 0;
Hi Cyril,
Thanks for yor review.
It seems better to me, and i will send the v2 patch.
Thanks,
Xiao Yang
> I will double check and test it later today.
>
next prev parent reply other threads:[~2018-09-13 4:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-13 9:48 [LTP] [PATCH] lib/tst_device.c: Make sure all loop deivces fot test are detached Xiao Yang
2018-09-12 12:33 ` Cyril Hrubis
2018-09-13 4:17 ` Xiao Yang [this message]
2018-09-13 5:22 ` [LTP] [PATCH v2] " Xiao Yang
2018-09-13 15:54 ` Cyril Hrubis
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=5B99E4D3.7070408@cn.fujitsu.com \
--to=yangx.jy@cn.fujitsu.com \
--cc=ltp@lists.linux.it \
/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