From: Karel Zak <kzak@redhat.com>
To: Ruediger Meier <sweet_f_a@gmx.de>
Cc: util-linux@vger.kernel.org
Subject: Re: losesetup -f, broken error handling
Date: Wed, 14 May 2014 13:04:50 +0200 [thread overview]
Message-ID: <20140514110450.GC26357@x2.net.home> (raw)
In-Reply-To: <201405132311.40706.sweet_f_a@gmx.de>
On Tue, May 13, 2014 at 11:11:40PM +0200, Ruediger Meier wrote:
> Below the otput of following commands. For comparison the first losetupfrom PATH
> is the installed one util-linux 2.20.1. Full build log here
> https://s3.amazonaws.com/archive.travis-ci.org/jobs/25104283/log.txt
The comparison is unnecessary as the code and semantic is very different.
Anyway, it's real issue, because on systems without /dev/loop-control
it might incorrectly returns loop0 although the device does not exist.
> lt-losetup from util-linux 2.24.749-4bbea
> ######## ./losetup -f
> /dev/loop0
> 0
I hope it's fixed now. Please, try it again.
Karel
--
Karel Zak <kzak@redhat.com>
http://karelzak.blogspot.com
next prev parent reply other threads:[~2014-05-14 11:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-12 13:10 losesetup -f, broken error handling Ruediger Meier
2014-05-13 9:20 ` Karel Zak
2014-05-13 21:11 ` Ruediger Meier
2014-05-14 11:04 ` Karel Zak [this message]
2014-05-14 12:56 ` Ruediger Meier
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=20140514110450.GC26357@x2.net.home \
--to=kzak@redhat.com \
--cc=sweet_f_a@gmx.de \
--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