qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Laurent Vivier <laurent@vivier.eu>
To: Shu-Chun Weng <scw@google.com>
Cc: arunkaly@google.com, riku.voipio@iki.fi,
	marcandre.lureau@gmail.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v3] linux-user: add memfd_create
Date: Tue, 10 Sep 2019 18:49:46 +0200	[thread overview]
Message-ID: <e5523e4b-1cf3-7b96-c064-7872def37c4f@vivier.eu> (raw)
In-Reply-To: <20190819180947.180725-1-scw@google.com>

On 19/08/2019 20:09, Shu-Chun Weng wrote:
> Add support for the memfd_create syscall. If the host does not have the
> libc wrapper, translate to a direct syscall with NC-macro.
> 
> Buglink: https://bugs.launchpad.net/qemu/+bug/1734792
> Signed-off-by: Shu-Chun Weng <scw@google.com>
> ---
>  include/qemu/memfd.h |  4 ++++
>  linux-user/syscall.c | 12 ++++++++++++
>  util/memfd.c         |  2 +-
>  3 files changed, 17 insertions(+), 1 deletion(-)

A nice follow up to this patch would be to implement the file-sealing
APIs provided by fnctl (see memfd_create(2) and fcntl(2), File sealing).

Thanks,
Laurent


  parent reply	other threads:[~2019-09-10 16:54 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-16 21:10 [Qemu-devel] [PATCH] linux-user: add memfd_create Shu-Chun Weng via Qemu-devel
2019-08-18 21:57 ` Philippe Mathieu-Daudé
2019-08-19  7:12 ` Marc-André Lureau
2019-08-19 11:56 ` Peter Maydell
2019-08-19 18:08   ` [Qemu-devel] [PATCH v2] " Shu-Chun Weng via Qemu-devel
2019-08-19 18:09   ` [Qemu-devel] [PATCH v3] " Shu-Chun Weng via Qemu-devel
2019-08-23 16:48     ` Laurent Vivier
2019-09-10 16:49     ` Laurent Vivier [this message]
2019-08-23 16:42   ` [Qemu-devel] [PATCH] " Laurent Vivier
2019-09-10  8:16 ` Laurent Vivier

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=e5523e4b-1cf3-7b96-c064-7872def37c4f@vivier.eu \
    --to=laurent@vivier.eu \
    --cc=arunkaly@google.com \
    --cc=marcandre.lureau@gmail.com \
    --cc=qemu-devel@nongnu.org \
    --cc=riku.voipio@iki.fi \
    --cc=scw@google.com \
    /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).