Patch "xtensa: provide __NR_sync_file_range2 instead of __NR_sync_file_range" has been added to the 3.10-stable tree
Subsystems (2)
This is a note to let you know that I've just added the patch titled
xtensa: provide __NR_sync_file_range2 instead of __NR_sync_file_range
to the 3.10-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
The filename of the patch is:
xtensa-provide-__nr_sync_file_range2-instead-of-__nr_sync_file_range.patch
and it can be found in the queue-3.10 subdirectory.
If you, or anyone else, feels it should not be added to the stable tree, please let <[email protected]> know about it.
Quoted 1 line
From
01e84c70fe40c8111f960987bcf7f931842e6d07Mon Sep 17 00:00:00 2001
From: Max Filippov <[email protected]>
Date: Fri, 27 Feb 2015 11:02:38 +0300
Subject: xtensa: provide __NR_sync_file_range2 instead of __NR_sync_file_range
From: Max Filippov <[email protected]>
commit 01e84c70fe40c8111f960987bcf7f931842e6d07 upstream.
xtensa actually uses sync_file_range2 implementation, so it should define __NR_sync_file_range2 as other architectures that use that function. That fixes userspace interface (that apparently never worked) and avoids special-casing xtensa in libc implementations. See the thread ending at
http://lists.busybox.net/pipermail/uclibc/2015-February/048833.html
for more details.
--- arch/xtensa/include/uapi/asm/unistd.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
arch/xtensa/include/uapi/asm/unistd.h +1 -1
@@ -715,7 +715,7 @@ __SYSCALL(323, sys_process_vm_writev, 6) __SYSCALL(324, sys_name_to_handle_at, 5)#define __NR_open_by_handle_at 325 __SYSCALL(325, sys_open_by_handle_at, 3) -#define __NR_sync_file_range 326 +#define __NR_sync_file_range2 326 __SYSCALL(326, sys_sync_file_range2, 6)#define __NR_perf_event_open 327__SYSCALL (327 , sys_perf_event_open,5 )
Patches currently in stable-queue which might be from [email protected] are
queue-3.10/xtensa-xtfpga-fix-hardware-lockup-caused-by-lcd-driver.patch queue-3.10/xtensa-provide-__nr_sync_file_range2-instead-of-__nr_sync_file_range.patch