From: James Wang <jnwang@suse.com>
To: osandov@fb.com
Cc: osandov@osandov.com, hch@infradead.org, axboe@fb.com,
hare@suse.com, linux-block@vger.kernel.org,
linux-kernel@vger.kernel.org, mgorman@suse.com,
James Wang <jnwang@suse.com>
Subject: [PATCH blktests v2] loop/002: Regression testing for loop device flush
Date: Tue, 27 Jun 2017 12:01:47 +0800 [thread overview]
Message-ID: <20170627040147.8823-1-jnwang@suse.com> (raw)
Add a regression testing for loop device. when an unbound device
be close that take too long time. kernel will consume serveral orders
of magnitude more wall time than it does for a mounted device.
Signed-off-by: James Wang <jnwang@suse.com>
---
tests/loop/002 | 63 ++++++++++++++++++++++++++++++++++++++++++++++++++++++
tests/loop/002.out | 2 ++
2 files changed, 65 insertions(+)
create mode 100755 tests/loop/002
create mode 100644 tests/loop/002.out
diff --git a/tests/loop/002 b/tests/loop/002
new file mode 100755
index 0000000..ef69729
--- /dev/null
+++ b/tests/loop/002
@@ -0,0 +1,63 @@
+#!/bin/bash
+#
+# Test if close()ing a unbound loop device is too slow
+# Copyright (C) 2017 James Wang <jnwang@suse.com>
+#
+# This program is free software: you can redistribute it and/or modify
+# it under the terms of the GNU General Public License as published by
+# the Free Software Foundation, either version 3 of the License, or
+# (at your option) any later version.
+#
+# This program is distributed in the hope that it will be useful,
+# but WITHOUT ANY WARRANTY; without even the implied warranty of
+# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
+# GNU General Public License for more details.
+#
+# You should have received a copy of the GNU General Public License
+# along with this program. If not, see <http://www.gnu.org/licenses/>.
+
+DESCRIPTION="Test if close()ing a unbound loop device is too slow"
+
+QUICK=1
+
+run_test() {
+ TIMEFORMAT='%5R'
+ time {
+ for ((i=0;i<200;i++)); do dd if=/dev/loop0 of=/dev/null bs=512 count=1 >/dev/null 2>&1; done
+ }
+}
+clean_up() {
+ if lsmod | grep loop >/dev/null 2>&1; then
+ if ! rmmod loop;then
+ return 2;
+ fi
+ fi
+}
+
+prepare() {
+ modprobe loop max_loop=1
+}
+
+
+test() {
+ echo "Running ${TEST_NAME}"
+
+ clean_up
+ prepare
+ SECONDS=0
+ run_test >/dev/null 2>&1
+ DURATION=${SECONDS}
+
+ clean_up
+ if ! clean_up; then
+ echo "Test complete"
+ return 2
+ fi
+ echo "Test complete"
+ if [[ "${DURATION}" -gt 1 ]]; then
+ echo "test took too long ($URATION seconds)"
+ return 1
+ else
+ return 0
+ fi
+}
diff --git a/tests/loop/002.out b/tests/loop/002.out
new file mode 100644
index 0000000..5c34a37
--- /dev/null
+++ b/tests/loop/002.out
@@ -0,0 +1,2 @@
+Running loop/002
+Test complete
--
2.12.3
next reply other threads:[~2017-06-27 4:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-27 4:01 James Wang [this message]
2017-08-18 8:11 ` Omar Sandoval
2017-08-18 10:09 ` James Wang
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=20170627040147.8823-1-jnwang@suse.com \
--to=jnwang@suse.com \
--cc=axboe@fb.com \
--cc=hare@suse.com \
--cc=hch@infradead.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.com \
--cc=osandov@fb.com \
--cc=osandov@osandov.com \
/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
all inboxes | Powered by JetHome®