ARG4, ARG5, ARG6);
PRE_REG_READ6(vki_size_t, "copy_file_range",
- int, "fd_in",
- vki_loff_t *, "off_in",
- int, "fd_out",
- vki_loff_t *, "off_out",
- vki_size_t, "len",
- unsigned int, "flags");
+ int, fd_in,
+ vki_loff_t *, off_in,
+ int, fd_out,
+ vki_loff_t *, off_out,
+ vki_size_t, len,
+ unsigned int, flags);
/* File descriptors are "specially" tracked by valgrind.
valgrind itself uses some, so make sure someone didn't
PRINT("pkey_alloc (%lu, %lu)", ARG1, ARG2);
PRE_REG_READ2(long, "pkey_alloc",
- unsigned long, "flags",
- unsigned long, "access_rights");
+ unsigned long, flags,
+ unsigned long, access_rights);
/* The kernel says: pkey_alloc() is always safe to call regardless of
whether or not the operating system supports protection keys. It can be
PRINT("pkey_free (%" FMT_REGWORD "u )", ARG1);
PRE_REG_READ1(long, "pkey_free",
- unsigned long, "pkey");
+ unsigned long, pkey);
/* Since pkey_alloc () can never succeed, see above, freeing any pkey is
always an error. */