From: Laurent Vivier <laurent@vivier.eu>
To: Filip Bozuta <filip.bozuta@syrmia.com>, qemu-devel@nongnu.org
Subject: Re: [PATCH v2 6/6] linux-user: Add strace support for printing arguments of fallocate()
Date: Wed, 10 Jun 2020 19:49:37 +0200 [thread overview]
Message-ID: <3d307eba-30c3-8663-ed89-a2a5ce5b3d80@vivier.eu> (raw)
In-Reply-To: <20200608164357.25065-7-filip.bozuta@syrmia.com>
Le 08/06/2020 à 18:43, Filip Bozuta a écrit :
> From: Filip Bozuta <Filip.Bozuta@syrmia.com>
>
> This patch implements strace argument printing functionality for following syscall:
>
> *fallocate - manipulate file space
>
> int fallocate(int fd, int mode, off_t offset, off_t len)
> man page: https://www.man7.org/linux/man-pages/man2/fallocate.2.html
>
> Implementation notes:
>
> This syscall's second argument "mode" is composed of predefined values
> which represent flags that determine the type of operation that is
> to be performed on the file space. For that reason, a printing
> function "print_fallocate" was stated in file "strace.list". This printing
> function uses an already existing function "print_flags()" to print flags of
> the "mode" argument. These flags are stated inside an array "falloc_flags"
> that contains values of type "struct flags". These values are instantiated
> using an existing macro "FLAG_GENERIC()". Most of these flags are defined
> after kernel version 3.0 which is why they are enwrapped in an #ifdef
> directive.
> The syscall's third ant fourth argument are of type "off_t" which can
> cause variations between 32/64-bit architectures. To handle this variation,
> function "target_offset64()" was copied from file "strace.c" and used in
> "print_fallocate" to print "off_t" arguments for 32-bit architectures.
>
> Signed-off-by: Filip Bozuta <Filip.Bozuta@syrmia.com>
> ---
> linux-user/qemu.h | 16 ++++++++++++++++
> linux-user/strace.c | 40 ++++++++++++++++++++++++++++++++++++++++
> linux-user/strace.list | 2 +-
> linux-user/syscall.c | 16 ----------------
> 4 files changed, 57 insertions(+), 17 deletions(-)
>
Reviewed-by: Laurent Vivier <laurent@vivier.eu>
next prev parent reply other threads:[~2020-06-10 17:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-08 16:43 [PATCH v2 0/6] Add strace support for printing arguments of selected syscalls Filip Bozuta
2020-06-08 16:43 ` [PATCH v2 1/6] linux-user: Extend strace support to enable argument printing after syscall execution Filip Bozuta
2020-06-10 17:33 ` Laurent Vivier
2020-06-08 16:43 ` [PATCH v2 2/6] linux-user: Add strace support for a group of syscalls Filip Bozuta
2020-06-08 16:43 ` [PATCH v2 3/6] linux-user: Add strace support for printing argument of syscalls used for extended attributes Filip Bozuta
2020-06-10 19:06 ` Laurent Vivier
2020-06-08 16:43 ` [PATCH v2 4/6] linux-user: Add strace support for printing arguments of lseek() Filip Bozuta
2020-06-10 17:58 ` Laurent Vivier
2020-06-08 16:43 ` [PATCH v2 5/6] linux-user: Add strace support for printing arguments of chown()/lchown() Filip Bozuta
2020-06-08 16:43 ` [PATCH v2 6/6] linux-user: Add strace support for printing arguments of fallocate() Filip Bozuta
2020-06-10 17:49 ` Laurent Vivier [this message]
2020-06-08 18:59 ` [PATCH v2 0/6] Add strace support for printing arguments of selected syscalls no-reply
2020-06-08 21:50 ` no-reply
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=3d307eba-30c3-8663-ed89-a2a5ce5b3d80@vivier.eu \
--to=laurent@vivier.eu \
--cc=filip.bozuta@syrmia.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).