From: Karel Zak <kzak@redhat.com>
To: Davidlohr Bueso <dave@gnu.org>
Cc: util-linux <util-linux@vger.kernel.org>
Subject: Re: [PATCH 0/5] losetup: rewrite
Date: Fri, 30 Sep 2011 11:35:07 +0200 [thread overview]
Message-ID: <20110930093507.GK19994@nb.net.home> (raw)
In-Reply-To: <1317066589.2896.0.camel@offbook>
On Mon, Sep 26, 2011 at 04:49:49PM -0300, Davidlohr Bueso wrote:
> Instead of a complete rewrite from scratch, like it was initially
> planned, its better to do it incrementally, which makes it easier to
> regression test.
I agree, do it incrementally is better for review. Anyway for merge
into master branch we need all changes.
Suggestion:
1. use directly lib/loopdev.c stuff in mount.c and umount.c
-- I did this yesterday. So you don't have to fight with
unreadable spaghetti in mount.c (check_loop() is hell)...
2. remove obsolete things (e.g. #ifdef !MAIN)
3. remove code around old non-64bit ioctls
4. remove lomount.h and loop.h (include/loopdev.h has to be enough)
5. move mount/lomount.c to sys-utils/losetup.c
6. use lib/loopdev.c stuff in sys-utils/losetup.c
- it should be possible to initialize one struct loopdev_cxt in main() and
use it in all operations
- rather than many variables (capacity, find, all, showdev,
assoc, delete, ...) use any enum for requested operation and
switch(command) as a core of the main().
Karel
--
Karel Zak <kzak@redhat.com>
http://karelzak.blogspot.com
prev parent reply other threads:[~2011-09-30 9:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-26 19:49 [PATCH 0/5] losetup: rewrite Davidlohr Bueso
2011-09-30 9:35 ` Karel Zak [this message]
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=20110930093507.GK19994@nb.net.home \
--to=kzak@redhat.com \
--cc=dave@gnu.org \
--cc=util-linux@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).