From: Zach Brown <zab@redhat.com>
To: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-btrfs@vger.kernel.org, linux-nfs@vger.kernel.org,
linux-scsi@vger.kernel.org
Subject: [PATCH RFC 2/3] x86: add sys_copy_file_range to syscall tables
Date: Fri, 10 Apr 2015 15:00:35 -0700 [thread overview]
Message-ID: <1428703236-24735-3-git-send-email-zab@redhat.com> (raw)
In-Reply-To: <1428703236-24735-1-git-send-email-zab@redhat.com>
Add sys_copy_file_range to the x86 syscall tables.
Signed-off-by: Zach Brown <zab@redhat.com>
---
arch/x86/syscalls/syscall_32.tbl | 1 +
arch/x86/syscalls/syscall_64.tbl | 1 +
2 files changed, 2 insertions(+)
diff --git a/arch/x86/syscalls/syscall_32.tbl b/arch/x86/syscalls/syscall_32.tbl
index b3560ec..88d0025 100644
--- a/arch/x86/syscalls/syscall_32.tbl
+++ b/arch/x86/syscalls/syscall_32.tbl
@@ -365,3 +365,4 @@
356 i386 memfd_create sys_memfd_create
357 i386 bpf sys_bpf
358 i386 execveat sys_execveat stub32_execveat
+359 i386 copy_file_range sys_copy_file_range
diff --git a/arch/x86/syscalls/syscall_64.tbl b/arch/x86/syscalls/syscall_64.tbl
index 8d656fb..81802c5 100644
--- a/arch/x86/syscalls/syscall_64.tbl
+++ b/arch/x86/syscalls/syscall_64.tbl
@@ -329,6 +329,7 @@
320 common kexec_file_load sys_kexec_file_load
321 common bpf sys_bpf
322 64 execveat stub_execveat
+323 common copy_file_range sys_copy_file_range
#
# x32-specific system call numbers start at 512 to avoid cache impact
--
2.1.0
next prev parent reply other threads:[~2015-04-10 22:00 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-10 22:00 [PATCH RFC 0/3] simple copy offloading system call Zach Brown
2015-04-10 22:00 ` [PATCH RFC 1/3] vfs: add copy_file_range syscall and vfs helper Zach Brown
[not found] ` <1428703236-24735-2-git-send-email-zab-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2015-04-10 22:36 ` Trond Myklebust
2015-04-11 0:02 ` Zach Brown
2015-04-11 0:24 ` Trond Myklebust
2015-04-11 13:04 ` Jeff Layton
2015-04-13 16:32 ` Zach Brown
2015-04-14 16:53 ` Christoph Hellwig
2015-04-14 16:58 ` Christoph Hellwig
[not found] ` <20150414165344.GA21421-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
2015-04-14 17:16 ` Anna Schumaker
[not found] ` <552D4B5D.3090904-ZwjVKphTwtPQT0dZR+AlfA@public.gmane.org>
2015-04-14 18:19 ` J. Bruce Fields
[not found] ` <20150414181911.GA2080-uC3wQj2KruNg9hUCZPvPmw@public.gmane.org>
2015-04-14 18:22 ` Zach Brown
[not found] ` <20150414182241.GB23129-fypN+1c5dIyjpB87vu3CluTW4wlIGRCZ@public.gmane.org>
2015-04-14 18:29 ` J. Bruce Fields
[not found] ` <20150414182906.GB2080-uC3wQj2KruNg9hUCZPvPmw@public.gmane.org>
2015-04-14 18:54 ` Zach Brown
[not found] ` <20150414185408.GC23129-fypN+1c5dIyjpB87vu3CluTW4wlIGRCZ@public.gmane.org>
2015-04-14 19:23 ` Christoph Hellwig
[not found] ` <20150414192325.GB20599-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
2015-04-14 20:04 ` Zach Brown
2015-04-10 23:01 ` Andreas Dilger
2015-04-10 22:00 ` Zach Brown [this message]
2015-04-10 22:00 ` [PATCH RFC 3/3] btrfs: add .copy_file_range file operation Zach Brown
2015-04-14 17:08 ` Chris Mason
[not found] ` <1428703236-24735-1-git-send-email-zab-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2015-05-06 6:15 ` [PATCH RFC 0/3] simple copy offloading system call Michael Kerrisk
2015-05-07 2:52 ` Andy Lutomirski
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=1428703236-24735-3-git-send-email-zab@redhat.com \
--to=zab@redhat.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=linux-scsi@vger.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).