All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Philippe Mathieu-Daudé" <f4bug@amsat.org>
To: Laurent Vivier <laurent@vivier.eu>, Riku Voipio <riku.voipio@iki.fi>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] linux-user: fix inotify
Date: Thu, 2 Mar 2017 00:55:20 -0300	[thread overview]
Message-ID: <aaa1d219-6f91-ed6c-179e-61adbcfa2b50@amsat.org> (raw)
In-Reply-To: <20170302005448.21336-1-laurent@vivier.eu>

On 03/01/2017 09:54 PM, Laurent Vivier wrote:
> When a fd is opened using inotify_init(), a read provides
> one or more inotify_event structures:
>
>     struct inotify_event {
>         int      wd;
>         uint32_t mask;
>         uint32_t cookie;
>         uint32_t len;
>         char     name[];
>     };
>
> The integer fields must be byte-swapped to the target endianness.
>
> Signed-off-by: Laurent Vivier <laurent@vivier.eu>

Reviewed-by: Philippe Mathieu-Daudé <f4bug@amsat.org>

> ---
>  linux-user/syscall.c | 29 +++++++++++++++++++++++++++++
>  1 file changed, 29 insertions(+)
>
> diff --git a/linux-user/syscall.c b/linux-user/syscall.c
> index cec8428..c2c4f3a 100644
> --- a/linux-user/syscall.c
> +++ b/linux-user/syscall.c
> @@ -7671,6 +7671,33 @@ static target_timer_t get_timer_id(abi_long arg)
>      return timerid;
>  }
>
> +#if (defined(TARGET_NR_inotify_init) && defined(__NR_inotify_init)) || \
> +    (defined(CONFIG_INOTIFY1) && defined(TARGET_NR_inotify_init1) && \
> +     defined(__NR_inotify_init1))
> +static abi_long host_to_target_data_inotify(void *buf, size_t len)
> +{
> +    struct inotify_event *ev;
> +    int i;
> +    uint32_t name_len;
> +
> +    for (i = 0; i < len; i += sizeof(struct inotify_event) + name_len) {
> +        ev = (struct inotify_event *)((char *)buf + i);
> +        name_len = ev->len;
> +
> +        ev->wd = tswap32(ev->wd);
> +        ev->mask = tswap32(ev->mask);
> +        ev->cookie = tswap32(ev->cookie);
> +        ev->len = tswap32(name_len);
> +    }
> +
> +    return len;
> +}
> +
> +static TargetFdTrans target_inotify_trans = {
> +    .host_to_target_data = host_to_target_data_inotify,
> +};
> +#endif
> +
>  /* 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 that do_syscall() returns must be -TARGET_<errcode>. */
> @@ -11694,6 +11721,7 @@ abi_long do_syscall(void *cpu_env, int num, abi_long arg1,
>  #if defined(TARGET_NR_inotify_init) && defined(__NR_inotify_init)
>      case TARGET_NR_inotify_init:
>          ret = get_errno(sys_inotify_init());
> +        fd_trans_register(ret, &target_inotify_trans);
>          break;
>  #endif
>  #ifdef CONFIG_INOTIFY1
> @@ -11701,6 +11729,7 @@ abi_long do_syscall(void *cpu_env, int num, abi_long arg1,
>      case TARGET_NR_inotify_init1:
>          ret = get_errno(sys_inotify_init1(target_to_host_bitmask(arg1,
>                                            fcntl_flags_tbl)));
> +        fd_trans_register(ret, &target_inotify_trans);
>          break;
>  #endif
>  #endif
>

  reply	other threads:[~2017-03-02  3:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-02  0:54 [Qemu-devel] [PATCH] linux-user: fix inotify Laurent Vivier
2017-03-02  3:55 ` Philippe Mathieu-Daudé [this message]
2017-04-25 16:33 ` 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=aaa1d219-6f91-ed6c-179e-61adbcfa2b50@amsat.org \
    --to=f4bug@amsat.org \
    --cc=laurent@vivier.eu \
    --cc=qemu-devel@nongnu.org \
    --cc=riku.voipio@iki.fi \
    /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.