From: Karel Zak <kzak@redhat.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: hooanon05@yahoo.co.jp, tomas@slax.org,
linux-kernel@vger.kernel.org, akinobu.mita@gmail.com,
util-linux-ng@vger.kernel.org
Subject: Re: [PATCH] loop file resizable
Date: Fri, 21 Nov 2008 11:12:09 +0100 [thread overview]
Message-ID: <20081121101209.GJ2961@nb.net.home> (raw)
In-Reply-To: <20081120132654.4c649eb0.akpm@linux-foundation.org>
On Thu, Nov 20, 2008 at 01:26:54PM -0800, Andrew Morton wrote:
> Well if we're going to do this then I guess we'll need to tell the
> util-linux people about it, as users will be needing some tool with
> which to access the new fucntionality.
>
> Presumably that would be some enhancement to losetup, or perhaps a new
> tool. Could the util-linux people please have a think about this and
> comment?
It shouldn't be a problem to extend the current losetup(8). I have no
problem with this change.
> Also, I'm not sure that the user interface is terribly good. The user
> must extend the file size and then we tell the loop driver to use all
> of the new file size. it would be better (more flexible) to allow
> userspace to explicitly pass in the new size for the loop device.
>
> But I'm not sure that this is worth bothering about.
I think the interface is useful and kernel side is pretty simple.
Karel
--
Karel Zak <kzak@redhat.com>
next prev parent reply other threads:[~2008-11-21 10:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-17 7:44 Tomas M
2008-11-19 0:42 ` Andrew Morton
2008-11-19 2:07 ` Akinobu Mita
2008-11-19 3:51 ` hooanon05
2008-11-19 18:34 ` Tomas M
2008-11-20 21:26 ` Andrew Morton
2008-11-21 2:37 ` hooanon05
2008-11-21 3:19 ` hooanon05
2008-11-21 4:31 ` [PATCH v2] " hooanon05
2008-11-21 10:12 ` Karel Zak [this message]
2008-11-21 12:23 ` [PATCH] " hooanon05
2008-11-21 12:44 ` Karel Zak
2008-11-24 2:08 ` hooanon05
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=20081121101209.GJ2961@nb.net.home \
--to=kzak@redhat.com \
--cc=akinobu.mita@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=hooanon05@yahoo.co.jp \
--cc=linux-kernel@vger.kernel.org \
--cc=tomas@slax.org \
--cc=util-linux-ng@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
all inboxes | Powered by JetHome®