From: Michael Ellerman <mpe@ellerman.id.au>
To: Christian Brauner <christian@brauner.io>,
viro@zeniv.linux.org.uk, linux-kernel@vger.kernel.org,
linux-fsdevel@vger.kernel.org, torvalds@linux-foundation.org,
fweimer@redhat.com
Cc: jannh@google.com, oleg@redhat.com, tglx@linutronix.de,
arnd@arndb.de, shuah@kernel.org, dhowells@redhat.com,
tkjos@android.com, ldv@altlinux.org, miklos@szeredi.hu,
Christian Brauner <christian@brauner.io>,
linux-api@vger.kernel.org, linux-alpha@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-ia64@vger.kernel.org,
linux-m68k@lists.linux-m68k.org, linux-mips@vger.kernel.org,
linux-parisc@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
linux-s390@vger.kernel.org, linux-sh@vger.kernel.org,
sparclinux@vger.kernel.org, linux-xtensa@linux-xtensa.org,
linux-arch@vger.kernel.org, x86@kernel.org
Subject: Re: [PATCH v3 2/3] arch: wire-up close_range()
Date: Tue, 28 May 2019 13:43:43 +1000 [thread overview]
Message-ID: <87woibp7kg.fsf@concordia.ellerman.id.au> (raw)
In-Reply-To: <20190524111047.6892-3-christian@brauner.io>
Christian Brauner <christian@brauner.io> writes:
> 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
next prev parent reply other threads:[~2019-05-28 3:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-24 11:10 [PATCH v3 0/3] close_range() Christian Brauner
2019-05-24 11:10 ` [PATCH v3 1/3] open: add close_range() Christian Brauner
2019-05-24 11:10 ` [PATCH v3 2/3] arch: wire-up close_range() Christian Brauner
2019-05-28 3:43 ` Michael Ellerman [this message]
2019-05-24 11:10 ` [PATCH v3 3/3] tests: add close_range() tests Christian Brauner
2019-05-28 3:22 ` Michael Ellerman
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=87woibp7kg.fsf@concordia.ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=arnd@arndb.de \
--cc=christian@brauner.io \
--cc=dhowells@redhat.com \
--cc=fweimer@redhat.com \
--cc=jannh@google.com \
--cc=ldv@altlinux.org \
--cc=linux-alpha@vger.kernel.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux-parisc@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=linux-xtensa@linux-xtensa.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=miklos@szeredi.hu \
--cc=oleg@redhat.com \
--cc=shuah@kernel.org \
--cc=sparclinux@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=tkjos@android.com \
--cc=torvalds@linux-foundation.org \
--cc=viro@zeniv.linux.org.uk \
--cc=x86@kernel.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).