From: Tomas Racek <tracek@redhat.com>
To: xfs@oss.sgi.com
Cc: lczerner@redhat.com, Tomas Racek <tracek@redhat.com>
Subject: [PATCH 2/3 V2] Add new standard loop handling functions
Date: Tue, 12 Feb 2013 10:21:59 +0100 [thread overview]
Message-ID: <1360660919-13535-1-git-send-email-tracek@redhat.com> (raw)
Add _create_loop_device and _destroy_loop_device to uniformly handle
loopback devices.
V1->V2: Fix possible race
Signed-off-by: Tomas Racek <tracek@redhat.com>
---
common.rc | 13 +++++++++++++
1 file changed, 13 insertions(+)
diff --git a/common.rc b/common.rc
index 0cccb94..2f4a9f4 100644
--- a/common.rc
+++ b/common.rc
@@ -1833,6 +1833,19 @@ _require_dumpe2fs()
fi
}
+_create_loop_device()
+{
+ file=$1
+ dev=`losetup -f --show $file` || _fail "Cannot assign $file to a loop device"
+ echo $dev
+}
+
+_destroy_loop_device()
+{
+ dev=$1
+ losetup -d $dev || _fail "Cannot destroy loop device $dev"
+}
+
################################################################################
if [ "$iam" != new -a "$iam" != bench ]
--
1.7.11.7
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
reply other threads:[~2013-02-12 9:22 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1360660919-13535-1-git-send-email-tracek@redhat.com \
--to=tracek@redhat.com \
--cc=lczerner@redhat.com \
--cc=xfs@oss.sgi.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