From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:46801)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <kraxel@redhat.com>) id 1afpuG-0004Ka-Dt
	for qemu-devel@nongnu.org; Tue, 15 Mar 2016 10:25:09 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <kraxel@redhat.com>) id 1afpuD-0003dR-87
	for qemu-devel@nongnu.org; Tue, 15 Mar 2016 10:25:08 -0400
Received: from mx1.redhat.com ([209.132.183.28]:39408)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <kraxel@redhat.com>) id 1afpuD-0003cy-3e
	for qemu-devel@nongnu.org; Tue, 15 Mar 2016 10:25:05 -0400
Message-ID: <1458051901.13231.78.camel@redhat.com>
From: Gerd Hoffmann <kraxel@redhat.com>
Date: Tue, 15 Mar 2016 15:25:01 +0100
In-Reply-To: <56E818BD.2080906@redhat.com>
References: <1458050002-27741-1-git-send-email-mst@redhat.com>
	<56E818BD.2080906@redhat.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0
Subject: Re: [Qemu-devel] [PATCH] vl.c: disallow command line fw cfg without
	opt/
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Corey Minyard <cminyard@mvista.com>, qemu-devel@nongnu.org, "Michael S. Tsirkin" <mst@redhat.com>

On Di, 2016-03-15 at 15:14 +0100, Paolo Bonzini wrote:
>=20
> On 15/03/2016 14:55, Michael S. Tsirkin wrote:
> > Allowing arbitary file names on command line is setting us up for
> > failure: future guests will look for a specific QEMU-specified name and
> > will get confused finding a user file there.
> >=20
> > Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
>=20
> Too bad for the user.
>=20
> I think we have already gone through this discussion.

Indeed, we discussed that before.

If users ignore the warning it's their fault.

Being able to set entries outside opt/ can be useful for debugging and
development purposes, this is the reason it is a warning only and not a
hard error.

cheers,
  Gerd