From: Warner Losh <imp@bsdimp.com>
To: qemu-devel@nongnu.org
Cc: Kyle Evans <kevans@freebsd.org>, Warner Losh <imp@bsdimp.com>
Subject: [PULL 00/11] Bsd user syscall 2022q2b patches
Date: Sat, 2 Jul 2022 07:56:55 -0600 [thread overview]
Message-ID: <20220702135706.73622-1-imp@bsdimp.com> (raw)
The following changes since commit d495e432c04a6394126c35cf96517749708b410f:
Merge tag 'pull-aspeed-20220630' of https://github.com/legoater/qemu into staging (2022-06-30 22:04:12 +0530)
are available in the Git repository at:
ssh://git@github.com/qemu-bsd-user/qemu-bsd-user.git tags/bsd-user-syscall-2022q2b-pull-request
for you to fetch changes up to 3f1b0235f68ff74ebfd98b17626e4254c4345fa8:
bsd-user: Remove stray 'inline' from do_bsd_close (2022-07-02 07:52:48 -0600)
----------------------------------------------------------------
bsd-user: More file-related system calls
A second round of mostly BSD-independent filesystem calls: mount, unmount,
nmount, symlink, symlinkat, readlink, readlinkat, chmod, fchmod, lchmod,
fchmodat, freebsd11_mknod, freebsd11_monodat, mknodat, chown, fchown, lchown,
fchownat, chflags, lchflags, fchflags, chroot, flock, mkfifo, mkfifoat,
pathconf, lpathconf, fpathconf, undelete.
These are all non-reentrant system calls, so these wrappers are pretty simple
and no safe_* versions need to be created.
----------------------------------------------------------------
Warner Losh (11):
bsd-user: Implement mount, umount and nmount
bsd-user: Implement symlink, symlinkat, readlink and readlinkat
bsd-user: implement chmod, fchmod, lchmod and fchmodat
bsd-user: Implement freebsd11_mknod, freebsd11_mknodat and mknodat
bsd-user: Implement chown, fchown, lchown and fchownat
bsd-user: Implement chflags, lchflags and fchflags
bsd-user: Implement chroot and flock
bsd-user: Implement mkfifo and mkfifoat
bsd-user: Implement pathconf, lpathconf and fpathconf
bsd-user: Implement undelete
bsd-user: Remove stray 'inline' from do_bsd_close
bsd-user/bsd-file.h | 392 +++++++++++++++++++++++++++++++++-
bsd-user/freebsd/os-syscall.c | 118 ++++++++++
2 files changed, 509 insertions(+), 1 deletion(-)
--
2.33.1
next reply other threads:[~2022-07-02 14:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-02 13:56 Warner Losh [this message]
2022-07-02 13:56 ` [PULL 01/11] bsd-user: Implement mount, umount and nmount Warner Losh
2022-07-02 13:56 ` [PULL 02/11] bsd-user: Implement symlink, symlinkat, readlink and readlinkat Warner Losh
2022-07-02 13:56 ` [PULL 03/11] bsd-user: implement chmod, fchmod, lchmod and fchmodat Warner Losh
2022-07-02 13:56 ` [PULL 04/11] bsd-user: Implement freebsd11_mknod, freebsd11_mknodat and mknodat Warner Losh
2022-07-02 13:57 ` [PULL 05/11] bsd-user: Implement chown, fchown, lchown and fchownat Warner Losh
2022-07-02 13:57 ` [PULL 06/11] bsd-user: Implement chflags, lchflags and fchflags Warner Losh
2022-07-02 13:57 ` [PULL 07/11] bsd-user: Implement chroot and flock Warner Losh
2022-07-02 13:57 ` [PULL 08/11] bsd-user: Implement mkfifo and mkfifoat Warner Losh
2022-07-02 13:57 ` [PULL 09/11] bsd-user: Implement pathconf, lpathconf and fpathconf Warner Losh
2022-07-02 13:57 ` [PULL 10/11] bsd-user: Implement undelete Warner Losh
2022-07-02 13:57 ` [PULL 11/11] bsd-user: Remove stray 'inline' from do_bsd_close Warner Losh
2022-07-03 0:58 ` [PULL 00/11] Bsd user syscall 2022q2b patches 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=20220702135706.73622-1-imp@bsdimp.com \
--to=imp@bsdimp.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.