From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:33031) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cjnOC-0007Oi-3P for qemu-devel@nongnu.org; Fri, 03 Mar 2017 08:36:56 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cjnOB-0000i6-5q for qemu-devel@nongnu.org; Fri, 03 Mar 2017 08:36:56 -0500 Date: Fri, 3 Mar 2017 14:36:45 +0100 From: Kevin Wolf Message-ID: <20170303133644.GC14351@noname.redhat.com> References: <1488491046-2549-1-git-send-email-armbru@redhat.com> <1488491046-2549-8-git-send-email-armbru@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1488491046-2549-8-git-send-email-armbru@redhat.com> Subject: Re: [Qemu-devel] [PATCH 07/15] sheepdog: Report errors in pseudo-filename more usefully List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Markus Armbruster Cc: qemu-devel@nongnu.org, qemu-block@nongnu.org, mitake.hitoshi@lab.ntt.co.jp, namei.unix@gmail.com, jcody@redhat.com Am 02.03.2017 um 22:43 hat Markus Armbruster geschrieben: > Errors in the pseudo-filename are all reported with the same laconic > "Can't parse filename" message. > > Add real error reporting, such as: > > $ qemu-system-x86_64 --drive driver=sheepdog,filename=sheepdog:/// > qemu-system-x86_64: --drive driver=sheepdog,filename=sheepdog:///: missing file path in URI > $ qemu-system-x86_64 --drive driver=sheepdog,filename=sheepgod:///vdi > qemu-system-x86_64: --drive driver=sheepdog,filename=sheepgod:///vdi: URI scheme must be 'sheepdog', 'sheepdog+tcp', or 'sheepdog+unix' > $ qemu-system-x86_64 --drive driver=sheepdog,filename=sheepdog+unix:///vdi?socke=sheepdog.sock > qemu-system-x86_64: --drive driver=sheepdog,filename=sheepdog+unix:///vdi?socke=sheepdog.sock: unexpected query parameters > > The code to translate legacy syntax to URI fails to escape URI > meta-characters. The new error messages are misleading then. Replace > them by the old "Can't parse filename" message. "Internal error" > would be more honest. Anyway, no worse than before. Also add a FIXME > comment. > > Signed-off-by: Markus Armbruster More upper/lower case inconsistency in error messages. Maybe I should simply ignore it. Reviewed-by: Kevin Wolf