503641 close_range syscalls started failing with 3.25.0
503677 duplicated-cond compiler warning in dis_RV64M
503817 s390x: fix 'ordered comparison of pointer with integer zero' compiler warnings
+503914 mount syscall param filesystemtype may be NULL
To see details of a given bug, visit
https://bugs.kde.org/show_bug.cgi?id=XXXXXX
{
// Nb: depending on 'flags', the 'type' and 'data' args may be ignored.
// We are conservative and check everything, except the memory pointed to
- // by 'data'.
+ // by 'data'. And since both 'source' and 'type' may be ignored, we allow
+ // them to be NULL.
*flags |= SfMayBlock;
PRINT("sys_mount( %#" FMT_REGWORD "x(%s), %#" FMT_REGWORD "x(%s), %#"
FMT_REGWORD "x(%s), %#" FMT_REGWORD "x, %#" FMT_REGWORD "x )",
if (ARG1)
PRE_MEM_RASCIIZ( "mount(source)", ARG1);
PRE_MEM_RASCIIZ( "mount(target)", ARG2);
- PRE_MEM_RASCIIZ( "mount(type)", ARG3);
+ if (ARG3)
+ PRE_MEM_RASCIIZ( "mount(type)", ARG3);
}
PRE(sys_oldumount)
// __NR_mount 21
GO(__NR_mount, "5s 3m");
- SY(__NR_mount, x0, x0, x0, x0, x0); FAIL;
+ SY(__NR_mount, x0, x0, x0-1, x0, x0); FAIL;
// __NR_umount arm64 only has umount2
//GO(__NR_umount, "1s 1m");
// __NR_mount 21
GO(__NR_mount, "5s 3m");
- SY(__NR_mount, x0, x0, x0, x0, x0); FAIL;
+ SY(__NR_mount, x0, x0, x0-1, x0, x0); FAIL;
// __NR_umount 22
GO(__NR_umount, "1s 1m");