From: nirbheek.chauhan@collabora.co.uk
To: linux-btrfs@vger.kernel.org
Cc: Nirbheek Chauhan <nirbheek.chauhan@collabora.co.uk>
Subject: [PATCH] Btrfs-progs: loopback files cannot be used if the path is too long
Date: Fri, 12 Oct 2012 19:25:33 +0530 [thread overview]
Message-ID: <1350050134-12151-1-git-send-email-nirbheek.chauhan@collabora.co.uk> (raw)
From: Nirbheek Chauhan <nirbheek.chauhan@collabora.co.uk>
If the path to a given loopback file is longer than 64 characters, none of the
Btrfs-progs tools can use it. This is because the size of loopinfo.lo_name
returned by the LOOP_GET_STATUS ioctl is 64.
The attached patch fixes this by fetching the backing file for a loopback device
from /sys/block; which is how `losetup` from util-linux does it as well.
Nirbheek Chauhan (1):
Btrfs-progs: fix resolving of loop devices
utils.c | 26 ++++++++++++++------------
1 files changed, 14 insertions(+), 12 deletions(-)
--
1.7.8.6
next reply other threads:[~2012-10-12 13:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-12 13:55 nirbheek.chauhan [this message]
2012-10-12 13:55 ` [PATCH] Btrfs-progs: fix resolving of loop devices nirbheek.chauhan
2012-10-23 9:53 ` Hector Oron
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=1350050134-12151-1-git-send-email-nirbheek.chauhan@collabora.co.uk \
--to=nirbheek.chauhan@collabora.co.uk \
--cc=linux-btrfs@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).