From: Warner Losh <imp@bsdimp.com>
To: qemu-devel@nongnu.org
Cc: Kyle Evans <kevans@freebsd.org>, Warner Losh <imp@bsdimp.com>,
Stacey Son <sson@FreeBSD.org>,
Richard Henderson <richard.henderson@linaro.org>
Subject: [PATCH v2 07/11] bsd-user: Implement chroot and flock
Date: Fri, 24 Jun 2022 15:47:38 -0600 [thread overview]
Message-ID: <20220624214742.89229-8-imp@bsdimp.com> (raw)
In-Reply-To: <20220624214742.89229-1-imp@bsdimp.com>
Signed-off-by: Stacey Son <sson@FreeBSD.org>
Signed-off-by: Warner Losh <imp@bsdimp.com>
Reviewed-by: Richard Henderson <richard.henderson@linaro.org>
---
bsd-user/bsd-file.h | 19 +++++++++++++++++++
bsd-user/freebsd/os-syscall.c | 8 ++++++++
2 files changed, 27 insertions(+)
diff --git a/bsd-user/bsd-file.h b/bsd-user/bsd-file.h
index a1c80428d98..c24054fed11 100644
--- a/bsd-user/bsd-file.h
+++ b/bsd-user/bsd-file.h
@@ -848,4 +848,23 @@ static abi_long do_bsd_fchflags(abi_long arg1, abi_long arg2)
return get_errno(fchflags(arg1, arg2));
}
+/* chroot(2) */
+static abi_long do_bsd_chroot(abi_long arg1)
+{
+ abi_long ret;
+ void *p;
+
+ LOCK_PATH(p, arg1);
+ ret = get_errno(chroot(p)); /* XXX path(p)? */
+ UNLOCK_PATH(p, arg1);
+
+ return ret;
+}
+
+/* flock(2) */
+static abi_long do_bsd_flock(abi_long arg1, abi_long arg2)
+{
+ return get_errno(flock(arg1, arg2));
+}
+
#endif /* BSD_FILE_H */
diff --git a/bsd-user/freebsd/os-syscall.c b/bsd-user/freebsd/os-syscall.c
index 06bc76a326b..d252fb40737 100644
--- a/bsd-user/freebsd/os-syscall.c
+++ b/bsd-user/freebsd/os-syscall.c
@@ -459,6 +459,14 @@ static abi_long freebsd_syscall(void *cpu_env, int num, abi_long arg1,
ret = do_bsd_fchflags(arg1, arg2);
break;
+ case TARGET_FREEBSD_NR_chroot: /* chroot(2) */
+ ret = do_bsd_chroot(arg1);
+ break;
+
+ case TARGET_FREEBSD_NR_flock: /* flock(2) */
+ ret = do_bsd_flock(arg1, arg2);
+ break;
+
default:
qemu_log_mask(LOG_UNIMP, "Unsupported syscall: %d\n", num);
ret = -TARGET_ENOSYS;
--
2.33.1
next prev parent reply other threads:[~2022-06-24 21:53 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-24 21:47 [PATCH v2 00/11] bsd-user: More file-related system calls Warner Losh
2022-06-24 21:47 ` [PATCH v2 01/11] bsd-user: Implement mount, umount and nmount Warner Losh
2022-06-24 21:47 ` [PATCH v2 02/11] bsd-user: Implement symlink, symlinkat, readlink and readlinkat Warner Losh
2022-06-26 3:47 ` Richard Henderson
2022-06-24 21:47 ` [PATCH v2 03/11] bsd-user: implement chmod, fchmod, lchmod and fchmodat Warner Losh
2022-06-24 21:47 ` [PATCH v2 04/11] bsd-user: Implement freebsd11_mknod, freebsd11_mknodat and mknodat Warner Losh
2022-06-26 3:49 ` Richard Henderson
2022-06-24 21:47 ` [PATCH v2 05/11] bsd-user: Implement chown, fchown, lchown and fchownat Warner Losh
2022-06-24 21:47 ` [PATCH v2 06/11] bsd-user: Implement chflags, lchflags and fchflags Warner Losh
2022-06-24 21:47 ` Warner Losh [this message]
2022-06-24 21:47 ` [PATCH v2 08/11] bsd-user: Implement mkfifo and mkfifoat Warner Losh
2022-06-24 21:47 ` [PATCH v2 09/11] bsd-user: Implement pathconf, lpathconf and fpathconf Warner Losh
2022-06-24 21:47 ` [PATCH v2 10/11] bsd-user: Implement undelete Warner Losh
2022-06-24 21:47 ` [PATCH v2 11/11] bsd-user: Remove stray 'inline' from do_bsd_close Warner Losh
2022-06-26 3:49 ` Richard Henderson
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=20220624214742.89229-8-imp@bsdimp.com \
--to=imp@bsdimp.com \
--cc=kevans@freebsd.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=sson@FreeBSD.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).