Re: [PATCH v3 2/3] arch: wire-up close_range()
From: Michael Ellerman <mpe@ellerman.id.au>
Date: 2019-05-28 03:43:58
Also in:
linux-alpha, linux-api, linux-arch, linux-arm-kernel, linux-fsdevel, linux-mips, linux-s390, linux-sh, lkml, sparclinux
Christian Brauner [off-list ref] writes:
quoted hunk ↗ jump to hunk
diff --git a/arch/powerpc/kernel/syscalls/syscall.tbl b/arch/powerpc/kernel/syscalls/syscall.tbl index 103655d84b4b..ba2c1f078cbd 100644 --- a/arch/powerpc/kernel/syscalls/syscall.tbl +++ b/arch/powerpc/kernel/syscalls/syscall.tbl@@ -515,3 +515,4 @@ 431 common fsconfig sys_fsconfig 432 common fsmount sys_fsmount 433 common fspick sys_fspick +435 common close_range sys_close_range
With a minor build fix the selftest passes for me on ppc64le: # ./close_range_test 1..9 ok 1 do not allow invalid flag values for close_range() ok 2 close_range() from 3 to 53 ok 3 fcntl() verify closed range from 3 to 53 ok 4 close_range() from 54 to 95 ok 5 fcntl() verify closed range from 54 to 95 ok 6 close_range() from 96 to 102 ok 7 fcntl() verify closed range from 96 to 102 ok 8 close_range() closed single file descriptor ok 9 fcntl() verify closed single file descriptor # Pass 9 Fail 0 Xfail 0 Xpass 0 Skip 0 Error 0 Acked-by: Michael Ellerman <mpe@ellerman.id.au> (powerpc) cheers