From: Laurent Vivier <laurent@vivier.eu>
To: Aleksandar Markovic <aleksandar.markovic@rt-rk.com>,
qemu-devel@nongnu.org
Cc: amarkovic@wavecomp.com
Subject: Re: [PATCH 03/12] linux-user: Add support for FS_IOC32_<GET|SET>VERSION ioctls
Date: Wed, 22 Jan 2020 15:07:07 +0100 [thread overview]
Message-ID: <86937f48-7e08-684d-0c8f-2fb2fd4e3822@vivier.eu> (raw)
In-Reply-To: <1579214991-19602-4-git-send-email-aleksandar.markovic@rt-rk.com>
Le 16/01/2020 à 23:49, Aleksandar Markovic a écrit :
> From: Aleksandar Markovic <amarkovic@wavecomp.com>
>
> These FS_IOC32_<GET|SET>VERSION ioctls are identical to
> FS_IOC_<GET|SET>VERSION ioctls, but without the anomaly of their
> number defined as if their third argument is of type long, while
> it is treated internally in kernel as is of type int.
>
> Reviewed-by: Laurent Vivier <laurent@vivier.eu>
> Signed-off-by: Aleksandar Markovic <amarkovic@wavecomp.com>
> ---
> linux-user/ioctls.h | 2 ++
> linux-user/syscall_defs.h | 2 ++
> 2 files changed, 4 insertions(+)
>
> diff --git a/linux-user/ioctls.h b/linux-user/ioctls.h
> index 4fd6939..3affd88 100644
> --- a/linux-user/ioctls.h
> +++ b/linux-user/ioctls.h
> @@ -142,6 +142,8 @@
> IOCTL(FS_IOC_SETVERSION, IOC_W, MK_PTR(TYPE_INT))
> IOCTL(FS_IOC32_GETFLAGS, IOC_R, MK_PTR(TYPE_INT))
> IOCTL(FS_IOC32_SETFLAGS, IOC_W, MK_PTR(TYPE_INT))
> + IOCTL(FS_IOC32_GETVERSION, IOC_R, MK_PTR(TYPE_INT))
> + IOCTL(FS_IOC32_SETVERSION, IOC_W, MK_PTR(TYPE_INT))
>
> #ifdef CONFIG_USBFS
> /* USB ioctls */
> diff --git a/linux-user/syscall_defs.h b/linux-user/syscall_defs.h
> index 964b2b4..a73cc3d 100644
> --- a/linux-user/syscall_defs.h
> +++ b/linux-user/syscall_defs.h
> @@ -922,6 +922,8 @@ struct target_pollfd {
> #define TARGET_FS_IOC_FIEMAP TARGET_IOWR('f',11,struct fiemap)
> #define TARGET_FS_IOC32_GETFLAGS TARGET_IOR('f', 1, int)
> #define TARGET_FS_IOC32_SETFLAGS TARGET_IOW('f', 2, int)
> +#define TARGET_FS_IOC32_GETVERSION TARGET_IOR('v', 1, int)
> +#define TARGET_FS_IOC32_SETVERSION TARGET_IOW('v', 2, int)
>
> /* usb ioctls */
> #define TARGET_USBDEVFS_CONTROL TARGET_IOWRU('U', 0)
>
Applied to my linux-user branch.
Thanks,
Laurent
next prev parent reply other threads:[~2020-01-22 14:08 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-16 22:49 [PATCH 00/12] linux-user: Add support for fs, fd,and kcov ioctls Aleksandar Markovic
2020-01-16 22:49 ` [PATCH 01/12] linux-user: Add support for FS_IOC_<GET|SET>VERSION ioctls Aleksandar Markovic
2020-01-22 14:04 ` Laurent Vivier
2020-01-16 22:49 ` [PATCH 02/12] linux-user: Add support for FS_IOC32_<GET|SET>FLAGS ioctls Aleksandar Markovic
2020-01-22 14:06 ` Laurent Vivier
2020-01-16 22:49 ` [PATCH 03/12] linux-user: Add support for FS_IOC32_<GET|SET>VERSION ioctls Aleksandar Markovic
2020-01-22 14:07 ` Laurent Vivier [this message]
2020-01-16 22:49 ` [PATCH 04/12] linux-user: Add support for FS_IOC_FS<GET|SET>XATTR ioctls Aleksandar Markovic
2020-01-16 22:49 ` [PATCH 05/12] linux-user: Add support for FITRIM ioctl Aleksandar Markovic
2020-01-16 22:49 ` [PATCH 06/12] linux-user: Add support for FIFREEZE and FITHAW ioctls Aleksandar Markovic
2020-01-16 22:49 ` [PATCH 07/12] linux-user: Add support for FD<SETEMSGTRESH|SETMAXERRS|GETMAXERRS> ioctls Aleksandar Markovic
2020-01-22 14:13 ` Laurent Vivier
2020-01-16 22:49 ` [PATCH 08/12] linux-user: Add support for FDFMT<BEG|TRK|END> ioctls Aleksandar Markovic
2020-01-22 14:13 ` Laurent Vivier
2020-01-16 22:49 ` [PATCH 09/12] linux-user: Add support for FDGETFDCSTAT ioctl Aleksandar Markovic
2020-01-16 22:49 ` [PATCH 10/12] configure: Detect kcov support and introduce CONFIG_KCOV Aleksandar Markovic
2020-01-22 14:10 ` Laurent Vivier
2020-01-22 14:16 ` Laurent Vivier
2020-01-16 22:49 ` [PATCH 11/12] linux-user: Add support for KCOV_<ENABLE|DISABLE> ioctls Aleksandar Markovic
2020-01-22 14:16 ` Laurent Vivier
2020-01-16 22:49 ` [PATCH 12/12] linux-user: Add support for KCOV_INIT_TRACE ioctl Aleksandar Markovic
2020-01-22 14: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=86937f48-7e08-684d-0c8f-2fb2fd4e3822@vivier.eu \
--to=laurent@vivier.eu \
--cc=aleksandar.markovic@rt-rk.com \
--cc=amarkovic@wavecomp.com \
--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).