From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:59777)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <berrange@redhat.com>) id 1brP3P-0008DH-NL
	for qemu-devel@nongnu.org; Tue, 04 Oct 2016 08:42:42 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <berrange@redhat.com>) id 1brP3K-0005pc-Gj
	for qemu-devel@nongnu.org; Tue, 04 Oct 2016 08:42:38 -0400
Received: from mx1.redhat.com ([209.132.183.28]:54006)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <berrange@redhat.com>) id 1brP3K-0005pH-9V
	for qemu-devel@nongnu.org; Tue, 04 Oct 2016 08:42:34 -0400
Date: Tue, 4 Oct 2016 13:42:28 +0100
From: "Daniel P. Berrange" <berrange@redhat.com>
Message-ID: <20161004124228.GI5578@redhat.com>
Reply-To: "Daniel P. Berrange" <berrange@redhat.com>
References: <20160927083626.GC3967@redhat.com>
	<7220810B-7C81-4B51-BDE5-7BC0022F3605@canonical.com>
	<20160927121841.GM3967@redhat.com>
	<3F76E640-1E36-4C4A-8BB9-1DD1EF602FEF@canonical.com>
	<20161003175539.GO13491@redhat.com>
	<DC1DD29F-BC29-41BD-957C-97DB3F3D3D5F@gmail.com>
	<BDC5F1BF-6DB2-4D00-9FF4-3E1219DABDE3@canonical.com>
	<20161004083628.GB5578@redhat.com>
	<F7883EE9-0100-49E7-B408-3F306A7B759B@canonical.com>
	<CAJ+F1CKpow8SKtoWN-ELwJS_9r+XpTYi3NUNYvKVr2Ai99s-jw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <CAJ+F1CKpow8SKtoWN-ELwJS_9r+XpTYi3NUNYvKVr2Ai99s-jw@mail.gmail.com>
Content-Transfer-Encoding: quoted-printable
Subject: Re: [Qemu-devel] [Bug 1626972] Re: [PATCH] util: secure
 memfd_create fallback mechanism
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: =?utf-8?Q?Marc-Andr=C3=A9?= Lureau <marcandre.lureau@gmail.com>
Cc: Rafael David Tinoco <rafael.tinoco@canonical.com>, Bug 1626972 <1626972@bugs.launchpad.net>, qemu-devel <qemu-devel@nongnu.org>

On Tue, Oct 04, 2016 at 12:39:17PM +0000, Marc-Andr=C3=A9 Lureau wrote:
> Hi Rafael, Daniel,
>=20
> On Tue, Oct 4, 2016 at 4:22 PM Rafael David Tinoco <
> rafael.tinoco@canonical.com> wrote:
>=20
> > Let me work on it. I'll get back soon.
> >
> >
> thanks for working on it, before that I have a few questions:
>=20
> Tks Daniel.
> >
> > > On Oct 04, 2016, at 05:36, Daniel P. Berrange <berrange@redhat.com>
> > wrote:
> > >
> > > On Mon, Oct 03, 2016 at 04:15:55PM -0300, Rafael David Tinoco wrote=
:
> > >> Yes, definitely. Check this:
> > >
> > > [snip]
> > >
> > > So in that case, I think we must add ability to specify an explicit=
 path
> > > that apps can use *regardles* of whether memfd support exists or no=
t.
> >
>=20
> How will this path be used? Is it going to be global to qemu for variou=
s
> use (kinda like $TMP), or per-device, or for memfd fallback only? Shoul=
d
> the path pre-exist? (I suppose, if not, qemu should clean it up when
> leaving)

I'd expect it to be an option set against the vhost user backend, since
that's the thing using this.

If other things have similar usage needs wrt memfd in future, they would
also need similar path config option.


Regards,
Daniel
--=20
|: http://berrange.com      -o-    http://www.flickr.com/photos/dberrange=
/ :|
|: http://libvirt.org              -o-             http://virt-manager.or=
g :|
|: http://entangle-photo.org       -o-    http://search.cpan.org/~danberr=
/ :|