On Thu, 21 Jul 2011 14:54:33 -0700 Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> wrote: > > > > The following patch attempts to achieve this by allowing a > > destination process, given an address and size from a source > > process, to copy memory directly from the source process into its > > own address space via a system call. There is also a symmetrical > > ability to copy from the current process's address space into a > > destination process's address space. > > > > ... > > > > arch/powerpc/include/asm/systbl.h | 2 > > arch/powerpc/include/asm/unistd.h | 4 > > arch/x86/include/asm/unistd_32.h | 4 > > arch/x86/kernel/syscall_table_32.S | 2 > > fs/aio.c | 4 > > fs/compat.c | 7 > > fs/read_write.c | 8 > > include/linux/compat.h | 3 > > include/linux/fs.h | 7 > > include/linux/syscalls.h | 13 + > > mm/Makefile | 3 > > mm/process_vm_access.c | 446 > > +++++++++++++++++++++++++++++++++++++ > > security/keys/compat.c | 2 > > security/keys/keyctl.c | 2 14 files changed, 490 > > insertions(+), 17 deletions(-) > > Confused. Why no arch/x86/include/asm/unistd_64.h wire-up? I forgot. Have done this now as well as the 32-bit compat and am retesting.... Chris -- cyeoh@xxxxxxxxxx -- To unsubscribe from this list: send the line "unsubscribe linux-man" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
