qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Warner Losh <imp@bsdimp.com>
To: qemu-devel@nongnu.org
Cc: arrowd@freebsd.org, def@freebsd.org, jrtc27@FreeBSD.org,
	Warner Losh <imp@bsdimp.com>, Kyle Evans <kevans@freebsd.org>
Subject: [PATCH 2/6] bsd-user/freebsd/os-syscall.c: unlock_iovec
Date: Tue,  7 Jun 2022 14:14:36 -0600	[thread overview]
Message-ID: <20220607201440.41464-3-imp@bsdimp.com> (raw)
In-Reply-To: <20220607201440.41464-1-imp@bsdimp.com>

Releases the references to the iovec created by lock_iovec.

Signed-off-by: Warner Losh <imp@bsdimp.com>
---
 bsd-user/freebsd/os-syscall.c | 14 ++++++++++++++
 1 file changed, 14 insertions(+)

diff --git a/bsd-user/freebsd/os-syscall.c b/bsd-user/freebsd/os-syscall.c
index c41ef0eda40..510307f29d9 100644
--- a/bsd-user/freebsd/os-syscall.c
+++ b/bsd-user/freebsd/os-syscall.c
@@ -186,6 +186,20 @@ fail2:
     return NULL;
 }
 
+void unlock_iovec(struct iovec *vec, abi_ulong target_addr,
+        int count, int copy)
+{
+    struct target_iovec *target_vec;
+
+    target_vec = lock_user(VERIFY_READ, target_addr,
+                           count * sizeof(struct target_iovec), 1);
+    if (target_vec) {
+        helper_unlock_iovec(target_vec, target_addr, vec, count, copy);
+    }
+
+    g_free(vec);
+}
+
 /*
  * do_syscall() should always have a single exit point at the end so that
  * actions, such as logging of syscall results, can be performed.  All errnos
-- 
2.33.1



  parent reply	other threads:[~2022-06-07 20:17 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-07 20:14 [PATCH 0/6] bsd-user upstreaming: read, write and exit Warner Losh
2022-06-07 20:14 ` [PATCH 1/6] bsd-user/freebsd/os-syscall.c: lock_iovec Warner Losh
2022-06-07 21:01   ` Richard Henderson
2022-06-07 21:31     ` Warner Losh
2022-06-07 20:14 ` Warner Losh [this message]
2022-06-07 21:28   ` [PATCH 2/6] bsd-user/freebsd/os-syscall.c: unlock_iovec Richard Henderson
2022-06-07 21:51     ` Warner Losh
2022-06-07 22:23       ` Richard Henderson
2022-06-07 23:35         ` Warner Losh
2022-06-08  2:02           ` Richard Henderson
2022-06-08 16:32             ` Warner Losh
2022-06-07 20:14 ` [PATCH 3/6] bsd-user/freebsd/os-syscall.c: Tracing and error boilerplate Warner Losh
2022-06-07 21:34   ` Richard Henderson
2022-06-07 21:56     ` Warner Losh
2022-06-07 20:14 ` [PATCH 4/6] bsd-user/bsd-file.h: Add implementations for read, pread, readv and preadv Warner Losh
2022-06-07 21:45   ` Richard Henderson
2022-06-08  2:02     ` Warner Losh
2022-06-07 20:14 ` [PATCH 5/6] bsd-user/bsd-file.h: Meat of the write system calls Warner Losh
2022-06-07 21:46   ` Richard Henderson
2022-06-07 20:14 ` [PATCH 6/6] bsd-user/freebsd/os-syscall.c: Implement exit Warner Losh

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=20220607201440.41464-3-imp@bsdimp.com \
    --to=imp@bsdimp.com \
    --cc=arrowd@freebsd.org \
    --cc=def@freebsd.org \
    --cc=jrtc27@FreeBSD.org \
    --cc=kevans@freebsd.org \
    --cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).