From: Richard Henderson <richard.henderson@linaro.org>
To: Warner Losh <imp@bsdimp.com>, qemu-devel@nongnu.org
Cc: Kyle Evans <kevans@freebsd.org>, Stacey Son <sson@FreeBSD.org>,
Michal Meloun <mmel@FreeBSD.org>
Subject: Re: [PATCH 04/10] bsd-user: Implement freebsd11_mknod, freebsd11_mknodat and mknodat
Date: Mon, 20 Jun 2022 12:13:35 -0700 [thread overview]
Message-ID: <76249ff6-cd3c-5b1c-f480-8c10c5b04429@linaro.org> (raw)
In-Reply-To: <20220620174220.22179-5-imp@bsdimp.com>
On 6/20/22 10:42, Warner Losh wrote:
> These implement both the old-pre INO64 mknod variations, as well as the
> now current INO64 variant. To implement the old stuff, we use some
> linker magic to bind to the old versions of these functions.
>
> Signed-off-by: Stacey Son <sson@FreeBSD.org>
> Signed-off-by: Michal Meloun <mmel@FreeBSD.org>
> Signed-off-by: Warner Losh <imp@bsdimp.com>
> ---
> bsd-user/bsd-file.h | 59 +++++++++++++++++++++++++++++++++++
> bsd-user/freebsd/os-syscall.c | 15 +++++++++
> 2 files changed, 74 insertions(+)
>
> diff --git a/bsd-user/bsd-file.h b/bsd-user/bsd-file.h
> index 0585f6a2a40..3be832b2a74 100644
> --- a/bsd-user/bsd-file.h
> +++ b/bsd-user/bsd-file.h
> @@ -51,6 +51,16 @@ do { \
> unlock_user(p1, arg1, 0); \
> } while (0)
>
> +#ifndef BSD_HAVE_INO64
> +#define freebsd11_mknod mknod
> +#define freebsd11_mknodat mknodat
> +#else
> +int freebsd11_mknod(char *path, mode_t mode, uint32_t dev);
> +__sym_compat(mknod, freebsd11_mknod, FBSD_1.0);
> +int freebsd11_mknodat(int fd, char *path, mode_t mode, uint32_t dev);
> +__sym_compat(mknodat, freebsd11_mknodat, FBSD_1.1);
> +#endif
Where does BSD_HAVE_INO64 come from? I can't find it defined in freebsd git.
You should probably avoid the linker tricks and use direct syscalls of
SYS_freebsd11_mknodat etc.
r~
next prev parent reply other threads:[~2022-06-20 19:16 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-20 17:42 [PATCH 00/10] bsd-user: More file-related system calls Warner Losh
2022-06-20 17:42 ` [PATCH 01/10] bsd-user: Implement mount, umount and nmount Warner Losh
2022-06-20 18:19 ` Richard Henderson
2022-06-20 17:42 ` [PATCH 02/10] bsd-user: Implement symlink, symlinkat, readlink and readlinkat Warner Losh
2022-06-20 18:28 ` Richard Henderson
2022-06-20 20:17 ` Warner Losh
2022-06-20 17:42 ` [PATCH 03/10] bsd-user: implement chmod, fchmod, lchmod and fchmodat Warner Losh
2022-06-20 18:37 ` Richard Henderson
2022-06-20 17:42 ` [PATCH 04/10] bsd-user: Implement freebsd11_mknod, freebsd11_mknodat and mknodat Warner Losh
2022-06-20 19:13 ` Richard Henderson [this message]
2022-06-20 20:32 ` Warner Losh
2022-06-20 17:42 ` [PATCH 05/10] bsd-user: Implement chown, fchown, lchown and fchownat Warner Losh
2022-06-20 19:18 ` Richard Henderson
2022-06-20 17:42 ` [PATCH 06/10] bsd-user: Implement chflags, lchflags and fchflags Warner Losh
2022-06-20 19:19 ` Richard Henderson
2022-06-20 17:42 ` [PATCH 07/10] bsd-user: Implement chroot and flock Warner Losh
2022-06-20 19:21 ` Richard Henderson
2022-06-20 17:42 ` [PATCH 08/10] bsd-user: Implement mkfifo and mkfifoat Warner Losh
2022-06-20 19:21 ` Richard Henderson
2022-06-20 17:42 ` [PATCH 09/10] bsd-user: Implement pathconf, lpathconf and fpathconf Warner Losh
2022-06-20 19:23 ` Richard Henderson
2022-06-20 17:42 ` [PATCH 10/10] bsd-user: Implement undelete Warner Losh
2022-06-20 19:23 ` 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=76249ff6-cd3c-5b1c-f480-8c10c5b04429@linaro.org \
--to=richard.henderson@linaro.org \
--cc=imp@bsdimp.com \
--cc=kevans@freebsd.org \
--cc=mmel@FreeBSD.org \
--cc=qemu-devel@nongnu.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).