qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Laurent Vivier <laurent@vivier.eu>
To: Filip Bozuta <filip.bozuta@syrmia.com>, qemu-devel@nongnu.org
Subject: Re: [PATCH v2 1/6] linux-user: Extend strace support to enable argument printing after syscall execution
Date: Wed, 10 Jun 2020 19:33:18 +0200	[thread overview]
Message-ID: <7da5b054-d378-10a7-f3a4-b3437baf00c3@vivier.eu> (raw)
In-Reply-To: <20200608164357.25065-2-filip.bozuta@syrmia.com>

Le 08/06/2020 à 18:43, Filip Bozuta a écrit :
> From: Filip Bozuta <Filip.Bozuta@syrmia.com>
> 
>     Structure "struct syscallname" in file "strace.c" is used for "-strace"
>     to print arguments and return values of syscalls. The last field of
>     this structure "result" represents the calling function that prints the
>     return values. This field was extended in this patch so that this functions
>     takes all syscalls arguments beside the return value. In this way, it enables
>     "-strace" to print arguments of syscalls that have changed after the syscall
>     execution. This extension will be useful as there are many syscalls that
>     return values inside their arguments (i.e. listxattr() that returns the list
>     of extended attributes inside the "list" argument).
> 
> Implementation notes:
> 
>     Since there are already three existing "print_syscall_ret*" functions inside
>     "strace.c" ("print_syscall_ret_addr()", "print_syscall_ret_adjtimex()",
>     "print_syscall_ret_newselect()"), they were changed to have all syscall arguments
>     beside the return value. This was done so that these functions don't cause build
>     errors (even though syscall arguments are not used in these functions).
> 
> Signed-off-by: Filip Bozuta <Filip.Bozuta@syrmia.com>
> ---
>  linux-user/qemu.h    |  4 +++-
>  linux-user/strace.c  | 24 ++++++++++++++++++------
>  linux-user/syscall.c |  2 +-
>  3 files changed, 22 insertions(+), 8 deletions(-)
> 

Reviewed-by: Laurent Vivier <laurent@vivier.eu>



  reply	other threads:[~2020-06-10 17:34 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 [this message]
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
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=7da5b054-d378-10a7-f3a4-b3437baf00c3@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).