Cross Memory Attach v3
Subsystems (11)
Hi Andrew,
Resending with CC's as you requested. Have added information about a man page and what is required for arches other than x86 and powerpc which have already been done.
Just as a reminder of what has happened so far, repeating some content from previous emails about it:
The basic idea behind cross memory attach is to allow MPI programs doing intra-node communication to do a single copy of the message rather than a double copy of the message via shared memory.
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.
- Use of /proc/pid/mem has been considered, but there are issues with using it:
- Does not allow for specifying iovecs for both src and dest, assuming preadv or pwritev was implemented either the area read from or
written to would need to be contiguous.
- Currently mem_read allows only processes who are currently ptrace'ing the target and are still able to ptrace the target to read from the target. This check could possibly be moved to the open call, but its not clear exactly what race this restriction is stopping (reason appears to have been lost)
- Having to send the fd of /proc/self/mem via SCM_RIGHTS on unix domain socket is a bit ugly from a userspace point of view, especially when you may have hundreds if not (eventually) thousands of processes that all need to do this with each other
- Doesn't allow for some future use of the interface we would like to consider adding in the future (see below)
- Interestingly reading from /proc/pid/mem currently actually involves two copies! (But this could be fixed pretty easily)
As mentioned previously use of vmsplice instead was considered, but has problems. Since you need the reader and writer working co-operatively if the pipe is not drained then you block. Which requires some wrapping to do non blocking on the send side or polling on the receive. In all to all communication it requires ordering otherwise you can deadlock. And in the example of many MPI tasks writing to one MPI task vmsplice serialises the copying.
There are some cases of MPI collectives where even a single copy interface does not get us the performance gain we could. For example in an MPI_Reduce rather than copy the data from the source we would like to instead use it directly in a mathops (say the reduce is doing a sum) as this would save us doing a copy. We don't need to keep a copy of the data from the source. I haven't implemented this, but I think this interface could in the future do all this through the use of the flags
- eg could specify the math operation and type and the kernel rather than just copying the data would apply the specified operation between the source and destination and store it in the destination.
Although we don't have a "second user" of the interface (though I've had some nibbles from people who may be interested in using it for intra process messaging which is not MPI). This interface is something which hardware vendors are already doing for their custom drivers to implement fast local communication. And so in addition to this being useful for OpenMPI it would mean the driver maintainers don't have to fix things up when the mm changes.
There was some discussion about how much faster a true zero copy would go. Here's a link back to the email with some testing I did on that:
http://marc.info/?l=linux-mm&m=130105930902915&w=2
There is a basic man page for the proposed interface here:
http://ozlabs.org/~cyeoh/cma/process_vm_readv.txt
This has been implemented for x86 and powerpc, other architecture should mainly (I think) just need to add syscall numbers for the process_vm_readv and process_vm_writev. There are 32 bit compatibility versions for 64-bit kernels.
For arch maintainers there are some simple tests to be able to quickly verify that the syscalls are working correctly here:
http://ozlabs.org/~cyeoh/cma/cma-test-20110718.tgz
Regards,
Chris
Signature · 18 lines
[email protected] Signed-off-by: Chris Yeoh <[email protected]> --- 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(-)
arch/powerpc/include/asm/systbl.h +2 -0
@@ -354,3 +354,5 @@ COMPAT_SYS_SPU(clock_adjtime) SYSCALL_SPU(syncfs) COMPAT_SYS_SPU(sendmmsg) SYSCALL_SPU(setns) +COMPAT_SYS(process_vm_readv) +COMPAT_SYS(process_vm_writev)
arch/powerpc/include/asm/unistd.h +3 -1
@@ -373,10 +373,12 @@#define __NR_syncfs 348#define __NR_sendmmsg 349#define __NR_setns 350 +#define __NR_process_vm_readv 351 +#define __NR_process_vm_writev 352#ifdef __KERNEL__ -#define __NR_syscalls 351 +#define __NR_syscalls 353#define __NR__exit __NR_exit#define NR_syscalls __NR_syscalls
arch/x86/include/asm/unistd_32.h +3 -1
@@ -352,10 +352,12 @@#define __NR_syncfs 344#define __NR_sendmmsg 345#define __NR_setns 346 +#define __NR_process_vm_readv 347 +#define __NR_process_vm_writev 348#ifdef __KERNEL__ -#define NR_syscalls 347 +#define NR_syscalls 349#define __ARCH_WANT_IPC_PARSE_VERSION#define __ARCH_WANT_OLD_READDIR
arch/x86/kernel/syscall_table_32.S +2 -0
@@ -346,3 +346,5 @@ ENTRY(sys_call_table) .long sys_syncfs .long sys_sendmmsg /* 345 */ .long sys_setns + .long sys_process_vm_readv + .long sys_process_vm_writev
fs/aio.c +2 -2
@@ -1387,13 +1387,13 @@ static ssize_t aio_setup_vectored_rw(int type, struct kiocb *kiocb, bool compat) ret =compat_rw_copy_check_uvector (type, (struct compat_iovec __user *)kiocb->ki_buf, kiocb->ki_nbytes,1 , &kiocb->ki_inline_vec, - &kiocb->ki_iovec); + &kiocb->ki_iovec,1 ); else#endif ret =rw_copy_check_uvector (type, (struct iovec __user *)kiocb->ki_buf, kiocb->ki_nbytes,1 , &kiocb->ki_inline_vec, - &kiocb->ki_iovec); + &kiocb->ki_iovec,1 );if (ret <0 ) goto out;
fs/compat.c +4 -3
@@ -550,7 +550,7 @@ out:ssize_t compat_rw_copy_check_uvector (int type,const struct compat_iovec __user *uvector,unsigned long nr_segs,unsigned long fast_segs,struct iovec *fast_pointer, -struct iovec **ret_pointer) +struct iovec **ret_pointer,int check_access) {compat_ssize_t tot_len;struct iovec *iov = *ret_pointer = fast_pointer;
@@ -597,7 +597,8 @@ ssize_t compat_rw_copy_check_uvector(int type, }if (len <0 )/* size_t not fitting in compat_ssize_t .. */ goto out; -if (!access_ok (vrfy_dir (type),compat_ptr (buf), len)) { +if (check_access && + !access_ok (vrfy_dir (type),compat_ptr (buf), len)) { ret = -EFAULT ; goto out; }
@@ -1111,7 +1112,7 @@ static ssize_t compat_do_readv_writev(int type, struct file *file, goto out; tot_len =compat_rw_copy_check_uvector (type, uvector, nr_segs, -UIO_FASTIOV , iovstack, &iov); +UIO_FASTIOV , iovstack, &iov,1 );if (tot_len ==0 ) { ret =0 ; goto out;
fs/read_write.c +5 -3
@@ -575,7 +575,8 @@ ssize_t do_loop_readv_writev(struct file *filp, struct iovec *iov,ssize_t rw_copy_check_uvector (int type,const struct iovec __user * uvector,unsigned long nr_segs,unsigned long fast_segs,struct iovec *fast_pointer, -struct iovec **ret_pointer) +struct iovec **ret_pointer, +int check_access) {unsigned long seg;ssize_t ret;
@@ -631,7 +632,8 @@ ssize_t rw_copy_check_uvector(int type, const struct iovec __user * uvector, ret = -EINVAL ; goto out; } -if (unlikely (!access_ok (vrfy_dir (type), buf, len))) { +if (check_access + &&unlikely (!access_ok (vrfy_dir (type), buf, len))) { ret = -EFAULT ; goto out; }
@@ -663,7 +665,7 @@ static ssize_t do_readv_writev(int type, struct file *file, } ret =rw_copy_check_uvector (type, uvector, nr_segs, -ARRAY_SIZE (iovstack), iovstack, &iov); +ARRAY_SIZE (iovstack), iovstack, &iov,1 );if (ret <=0 ) goto out;
include/linux/compat.h +2 -1
@@ -557,7 +557,8 @@ extern ssize_t compat_rw_copy_check_uvector(int type,const struct compat_iovec __user *uvector, unsigned long nr_segs, unsigned long fast_segs, struct iovec *fast_pointer, - struct iovec **ret_pointer); + struct iovec **ret_pointer, + int check_access);extern void __user *compat_alloc_user_space (unsigned long len);
include/linux/fs.h +4 -3
@@ -1608,9 +1608,10 @@ struct inode_operations {struct seq_file ;ssize_t rw_copy_check_uvector (int type,const struct iovec __user * uvector, -unsigned long nr_segs,unsigned long fast_segs, -struct iovec *fast_pointer, -struct iovec **ret_pointer); +unsigned long nr_segs,unsigned long fast_segs, +struct iovec *fast_pointer, +struct iovec **ret_pointer, +int check_access);extern ssize_t vfs_read (struct file *,char __user *,size_t ,loff_t *);extern ssize_t vfs_write (struct file *,const char __user *,size_t ,loff_t *);
include/linux/syscalls.h +13 -0
@@ -847,4 +847,17 @@ asmlinkage long sys_open_by_handle_at(int mountdirfd,struct file_handle __user *handle, int flags);asmlinkage long sys_setns (int fd,int nstype); +asmlinkage long sys_process_vm_readv (pid_t pid, +const struct iovec __user *lvec, +unsigned long liovcnt, +const struct iovec __user *rvec, +unsigned long riovcnt, +unsigned long flags); +asmlinkage long sys_process_vm_writev (pid_t pid, +const struct iovec __user *lvec, +unsigned long liovcnt, +const struct iovec __user *rvec, +unsigned long riovcnt, +unsigned long flags); +#endif
mm/Makefile +2 -1
@@ -5,7 +5,8 @@ mmu-y := nommu.o mmu-$(CONFIG_MMU) := fremap.o highmem.o madvise.o memory.o mincore.o \ mlock.o mmap.o mprotect.o mremap.o msync.o rmap.o \ - vmalloc.o pagewalk.o pgtable-generic.o + vmalloc.o pagewalk.o pgtable-generic.o \ + process_vm_access.o obj-y := filemap.o mempool.o oom_kill.o fadvise.o \ maccess.o page_alloc.o page-writeback.o \
mm/process_vm_access.c new file +446 -0
446 lines not on this page · raw message
security/keys/compat.c +1 -1
@@ -38,7 +38,7 @@ long compat_keyctl_instantiate_key_iov( ret =compat_rw_copy_check_uvector (WRITE , _payload_iov, ioc,ARRAY_SIZE (iovstack), - iovstack, &iov); + iovstack, &iov,1 );if (ret <0 )return ret;if (ret ==0 )
security/keys/keyctl.c +1 -1
@@ -1065,7 +1065,7 @@ long keyctl_instantiate_key_iov(key_serial_t id, goto no_payload; ret =rw_copy_check_uvector (WRITE , _payload_iov, ioc, -ARRAY_SIZE (iovstack), iovstack, &iov); +ARRAY_SIZE (iovstack), iovstack, &iov,1 );if (ret <0 )return ret;if (ret ==0 )
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to [email protected]. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"[email protected]"> [email protected] </a>
Andrew Morton
maintainerQuoted 22 lines · On Tue, 19 Jul 2011 00:35:37 +0930 Christopher Yeoh…
Hi Andrew,
Resending with CC's as you requested. Have added information about a man page and what is required for arches other than x86 and powerpc which have already been done.
Just as a reminder of what has happened so far, repeating some content from previous emails about it:
The basic idea behind cross memory attach is to allow MPI programs doing intra-node communication to do a single copy of the message rather than a double copy of the message via shared memory.
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.
...
Quoted 15 lines
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?
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
Quoted 27 lines · On Thu, 21 Jul 2011 14:54:33 -0700 Andrew Morton <[email protected]>…
Quoted 25 lines
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, 490Quoted 1 line
insertions(+), 17 deletions(-)
Quoted 1 line
Confused. Why no
arch/x86/include/asm/unistd_64.hwire-up?
I forgot. Have done this now as well as the 32-bit compat and am retesting....
Chris
Signature · 8 lines
[email protected] -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM, see: http://www.linux-mm.org/ . Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/ Don't email: <a href=mailto:"[email protected]"> [email protected] </a>
Andrew Morton
maintainerQuoted 78 lines · On Tue, 19 Jul 2011 00:35:37 +0930 Christopher Yeoh <[email protected]> wrote:
...
mm/process_vm_access.c new file +75
-0+/* +* process_vm_rw_pages - read/write pages from task specified +* @task: task to read/write from +* @mm: mm for task +* @process_pages: struct pages area that can store at least +* nr_pages_to_copy struct page pointers +* @pa: address of page in task to start copying from/to +* @start_offset: offset in page to start copying from/to +* @len: number of bytes to copy +* @lvec: iovec array specifying where to copy to/from +* @lvec_cnt: number of elements in iovec array +* @lvec_current: index in iovec array we are up to +* @lvec_offset: offset in bytes from current iovec iov_base we are up to +* @vm_write: 0 means copy from, 1 means copy to +* @nr_pages_to_copy: number of pages to copy +*/ +static ssize_t process_vm_rw_pages (struct task_struct *task, +struct mm_struct *mm, +struct page **process_pages, +unsigned long pa, +unsigned long start_offset, +unsigned long len, +const struct iovec *lvec, +unsigned long lvec_cnt, +unsigned long *lvec_current, +size_t *lvec_offset, +int vm_write, +unsigned int nr_pages_to_copy) +{ +int pages_pinned; +void *target_kaddr; +int pgs_copied =0 ; +int j; +int ret; +ssize_t bytes_to_copy; +ssize_t bytes_copied =0 ; +ssize_t rc = -EFAULT ; + +/* Get the pages we're interested in */ +down_read (&mm->mmap_sem); + pages_pinned =get_user_pages (task, mm, pa, + nr_pages_to_copy, + vm_write,0 , process_pages,NULL ); +up_read (&mm->mmap_sem); + +if (pages_pinned != nr_pages_to_copy) + goto end; + +/* Do the copy for each page */ +for (pgs_copied =0 ; + (pgs_copied < nr_pages_to_copy) && (*lvec_current < lvec_cnt); + pgs_copied++) { +/* Make sure we have a non zero length iovec */ +while (*lvec_current < lvec_cnt + && lvec[*lvec_current].iov_len ==0 ) + (*lvec_current)++; +if (*lvec_current == lvec_cnt) +break ; + +/* +* Will copy smallest of: +* - bytes remaining in page +* - bytes remaining in destination iovec +*/ + bytes_to_copy =min_t (ssize_t,PAGE_SIZE - start_offset, + len - bytes_copied); + bytes_to_copy =min_t (ssize_t, bytes_to_copy, + lvec[*lvec_current].iov_len + - *lvec_offset); + + target_kaddr =kmap (process_pages[pgs_copied]) + start_offset; + +if (vm_write) + ret =copy_from_user (target_kaddr, + lvec[*lvec_current].iov_base
mm/process_vm_access.c line 103
Quoted 10 lines
mm/process_vm_access.c new file +10
-0+ + *lvec_offset, + bytes_to_copy); + else + ret =copy_to_user (lvec[*lvec_current].iov_base + + *lvec_offset, + target_kaddr, bytes_to_copy); +kunmap (process_pages[pgs_copied]); +if (ret) { + pgs_copied++; + goto end;
afacit this will always return -EFAULT, even after copying some memory.
Is this a misdesign? Would it not be better to return the number of bytes actually copied, or -EFAULT is we weren't able to copy any? Like read().
That way, userspace can at least process the data which _was_ transferred, before retrying and then handling the fault. With the proposed interface this is not possible, and the data is lost.
And note that the function's kerneldoc doesn't document the return value at all! kerneldoc sucks that way - there's no formal place in the template, so people often ignore this important part of the function interface. Similarly, there's no kerneldoc template for preconditions such as irq on/off, locks which must be held, etc. So they don't get documented. But they're part of the interface.
Quoted 70 lines
mm/process_vm_access.c new file +67
-0+ } + bytes_copied += bytes_to_copy; + *lvec_offset += bytes_to_copy; +if (*lvec_offset == lvec[*lvec_current].iov_len) { +/* +* Need to copy remaining part of page into the +* next iovec if there are any bytes left in page +*/ + (*lvec_current)++; + *lvec_offset =0 ; + start_offset = (start_offset + bytes_to_copy) + %PAGE_SIZE ; +if (start_offset) + pgs_copied--; + }else { + start_offset =0 ; + } + } + + rc = bytes_copied; + +end: +if (vm_write) { +for (j =0 ; j < pages_pinned; j++) { +if (j < pgs_copied) +set_page_dirty_lock (process_pages[j]); +put_page (process_pages[j]); + } + }else { +for (j =0 ; j < pages_pinned; j++) +put_page (process_pages[j]); + } + +return rc; +} + +static ssize_t process_vm_rw_single_vec (unsigned long addr, +unsigned long len, +const struct iovec *lvec, +unsigned long lvec_cnt, +unsigned long *lvec_current, +size_t *lvec_offset, +struct page **process_pages, +struct mm_struct *mm, +struct task_struct *task, +int vm_write) +{ +unsigned long pa = addr &PAGE_MASK ; +unsigned long start_offset = addr - pa; +unsigned long nr_pages; +ssize_t bytes_copied =0 ; +ssize_t rc; +unsigned long nr_pages_copied =0 ; +unsigned long nr_pages_to_copy; +unsigned long max_pages_per_loop =PVM_MAX_KMALLOC_PAGES + /sizeof (struct pages *); + + +/* Work out address and page range required */ +if (len ==0 ) +return 0 ; + nr_pages = (addr + len -1 ) /PAGE_SIZE - addr /PAGE_SIZE +1 ; + + +while ((nr_pages_copied < nr_pages) && (*lvec_current < lvec_cnt)) { + nr_pages_to_copy =min (nr_pages - nr_pages_copied, + max_pages_per_loop);
mm/process_vm_access.c line 197
Quoted 10 lines
mm/process_vm_access.c new file +10
-0+ + rc =process_vm_rw_pages (task, mm, process_pages, pa, + start_offset, len, + lvec, lvec_cnt, + lvec_current, lvec_offset, + vm_write, nr_pages_to_copy); + start_offset =0 ; + +if (rc <0 ) +return rc;
It's propagated here.
(CodingStyleNit: it's conventional to put {} around the single-line block in this case, btw).
mm/process_vm_access.c line 203
Quoted 6 lines
mm/process_vm_access.c new file +6
-0+else { + bytes_copied += rc; + len -= rc; + nr_pages_copied += nr_pages_to_copy; + pa += nr_pages_to_copy *PAGE_SIZE ; + }
because this block had them.
Quoted 36 lines
mm/process_vm_access.c new file +36
-0+ } + + rc = bytes_copied; +return rc; +} + +static ssize_t process_vm_rw (pid_t pid,const struct iovec *lvec, +unsigned long liovcnt, +const struct iovec *rvec, +unsigned long riovcnt, +unsigned long flags,int vm_write) +{ +struct task_struct *task; +struct page **process_pages =NULL ; +struct mm_struct *mm; +unsigned long i; +ssize_t rc; +ssize_t bytes_copied; +unsigned long nr_pages =0 ; +unsigned long nr_pages_iov; +unsigned long iov_l_curr_idx =0 ; +size_t iov_l_curr_offset =0 ; +ssize_t iov_len; + +/* +* Work out how many pages of struct pages we're going to need +* when eventually calling get_user_pages +*/ +for (i =0 ; i < riovcnt; i++) { + iov_len = rvec[i].iov_len; +if (iov_len >0 ) { + nr_pages_iov = ((unsigned long )rvec[i].iov_base + + iov_len) + /PAGE_SIZE - (unsigned long )rvec[i].iov_base + /PAGE_SIZE +1 ; + nr_pages =max (nr_pages, nr_pages_iov);
mm/process_vm_access.c line 249
Quoted 10 lines
mm/process_vm_access.c new file +10
-0+ } + } + +if (nr_pages ==0 ) +return 0 ; + +/* For reliability don't try to kmalloc more than 2 pages worth */ + process_pages =kmalloc (min_t (size_t,PVM_MAX_KMALLOC_PAGES , +sizeof (struct pages *)*nr_pages), +GFP_KERNEL );
You might get some speed benefit by optimising for the small copies here. Define a local on-stack array of N page*'s and point process_pages at that if the number of pages is <= N. Saves a malloc/free and is more cache-friendly. But only if the result is measurable!
Quoted 53 lines
mm/process_vm_access.c new file +53
-0+if (!process_pages) +return -ENOMEM ; + +/* Get process information */ +rcu_read_lock (); + task =find_task_by_vpid (pid); +if (task) +get_task_struct (task); +rcu_read_unlock (); +if (!task) { + rc = -ESRCH ; + goto free_proc_pages; + } + +task_lock (task); +if (__ptrace_may_access (task,PTRACE_MODE_ATTACH )) { +task_unlock (task); + rc = -EPERM ; + goto put_task_struct; + } + mm = task->mm; + +if (!mm || (task->flags &PF_KTHREAD )) { +task_unlock (task); + rc = -EINVAL ; + goto put_task_struct; + } + +atomic_inc (&mm->mm_users); +task_unlock (task); + + rc =0 ; +for (i =0 ; i < riovcnt && iov_l_curr_idx < liovcnt; i++) { + bytes_copied =process_vm_rw_single_vec ( + (unsigned long )rvec[i].iov_base, rvec[i].iov_len, + lvec, liovcnt, &iov_l_curr_idx, &iov_l_curr_offset, + process_pages, mm, task, vm_write); +if (bytes_copied <0 ) { + rc = bytes_copied; + goto put_mm; + }else { + rc += bytes_copied; + } + } + +put_mm: +mmput (mm); + +put_task_struct: +put_task_struct (task); + + +free_proc_pages:
mm/process_vm_access.c line 313
Quoted 10 lines
mm/process_vm_access.c new file +10
-0+kfree (process_pages); +return rc; +} + +static ssize_t process_vm_rw_check_iovecs (pid_t pid, +const struct iovec __user *lvec, +unsigned long liovcnt, +const struct iovec __user *rvec, +unsigned long riovcnt, +unsigned long flags,int vm_write)
I'm allergic to functions with "check" in their name. Check for what?
And one would expect a check_foo() to return a bool or an errno. This one returns a ssize_t! Weird! Interface documentation, please. Including return value semantics ;)
Quoted 29 lines
mm/process_vm_access.c new file +28
-0+{ +struct iovec iovstack_l[UIO_FASTIOV ]; +struct iovec iovstack_r[UIO_FASTIOV ]; +struct iovec *iov_l = iovstack_l; +struct iovec *iov_r = iovstack_r; +ssize_t rc; + +if (flags !=0 ) +return -EINVAL ; + +/* Check iovecs */ +if (vm_write) + rc =rw_copy_check_uvector (WRITE , lvec, liovcnt,UIO_FASTIOV , + iovstack_l, &iov_l,1 ); +else + rc =rw_copy_check_uvector (READ , lvec, liovcnt,UIO_FASTIOV , + iovstack_l, &iov_l,1 ); +if (rc <=0 ) + goto free_iovecs; + + rc =rw_copy_check_uvector (READ , rvec, riovcnt,UIO_FASTIOV , + iovstack_r, &iov_r,0 ); +if (rc <=0 ) + goto free_iovecs; + + rc =process_vm_rw (pid, iov_l, liovcnt, iov_r, riovcnt, flags, + vm_write); +
mm/process_vm_access.c
Quoted 10 lines
mm/process_vm_access.c new file +8
-0+free_iovecs: +if (iov_r != iovstack_r) +kfree (iov_r); +if (iov_l != iovstack_l) +kfree (iov_l); + +return rc; +}
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to [email protected]. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"[email protected]"> [email protected] </a>
Quoted 48 lines · On Thu, 21 Jul 2011 15:09:08 -0700 Andrew Morton <[email protected]>…
Quoted 37 lines · On Tue, 19 Jul 2011 00:35:37 +0930 Christopher Yeoh <[email protected]> wrote:
+/*
+ *process_vm_rw_pages- read/write pages from task specified
+ * @task: task to read/write from
+ * @mm: mm for task
+ * @process_pages: struct pages area that can store at least
+ *nr_pages_to_copystruct page pointers
+ * @pa: address of page in task to start copying from/to
+ * @start_offset: offset in page to start copying from/to
+ * @len: number of bytes to copy
+ * @lvec: iovec array specifying where to copy to/from
+ * @lvec_cnt: number of elements in iovec array
+ * @lvec_current: index in iovec array we are up to
+ * @lvec_offset: offset in bytes from current ioveciov_basewe are up to
+ * @vm_write: 0 means copy from, 1 means copy to
+ * @nr_pages_to_copy: number of pages to copy
+ */mm/process_vm_access.c new file +5
-0+static ssize_t process_vm_rw_pages (struct task_struct *task, +struct mm_struct *mm, + - *lvec_offset); + + target_kaddr = kmap(process_pages[pgs_copied]) +
start_offset; +mm/process_vm_access.c new file +3
-0+if (vm_write) + ret = copy_from_user(target_kaddr, +lvec[*lvec_current].iov_base
mm/process_vm_access.c new file +4
-0+ + *lvec_offset, + bytes_to_copy); + else + ret =copy_to_user(lvec[*lvec_current].iov_base
(quoted diff) +2
-0+ + *lvec_offset, + target_kaddr,
bytes_to_copy);mm/process_vm_access.c line 103
Quoted 4 lines
mm/process_vm_access.c new file +4
-0+kunmap (process_pages[pgs_copied]); +if (ret) { + pgs_copied++; + goto end;afacit this will always return
-EFAULT, even after copying some memory.
Quoted 7 lines
Is this a misdesign? Would it not be better to return the number of bytes actually copied, or
-EFAULTis we weren't able to copy any? Likeread().That way, userspace can at least process the data which _was_ transferred, before retrying and then handling the fault. With the proposed interface this is not possible, and the data is lost.
Perhaps because of how I'm using the interface for MPI I
was thinking that if it fails at this point due to EFAULT then its an application error and that the partial read/write wouldn't be used. But I see your point could be true for other uses of the interface and the next version will return partial read/write information all the way back to userspace.
Quoted 7 lines
And note that the function's kerneldoc doesn't document the return value at all! kerneldoc sucks that way - there's no formal place in the template, so people often ignore this important part of the function interface. Similarly, there's no kerneldoc template for preconditions such as irq on/off, locks which must be held, etc. So they don't get documented. But they're part of the interface.
Ok. Will be fixed in next version
Quoted 11 lines
mm/process_vm_access.c line 197
Quoted 5 lines
nr_pages_to_copy);mm/process_vm_access.c new file +4
-0+ start_offset =0 ; + +if (rc <0 ) +return rc;It's propagated here.
(CodingStyleNit: it's conventional to put {} around the single-line block in this case, btw).
Fixed now.
Quoted 9 lines
Quoted 9 lines
mm/process_vm_access.c new file +5
-0+ +if (nr_pages ==0 ) +return 0 ; + +/* For reliability don't try to kmalloc more than 2 pages worth */
(quoted diff) +1
-0+ process_pages = kmalloc(min_t(size_t,
PVM_MAX_KMALLOC_PAGES,(quoted diff) +1
-0+ sizeof(struct pages
Quoted 8 lines
mm/process_vm_access.c line 249
Quoted 2 lines
*)*nr_pages),
mm/process_vm_access.c new file +1
-0+ GFP_KERNEL);You might get some speed benefit by optimising for the small copies here. Define a local on-stack array of N page*'s and point
process_pagesat that if the number of pages is <= N. Saves a malloc/free and is more cache-friendly. But only if the result is measurable!
ok. will do some benchmarking to see if its worth it.
Quoted 13 lines
Quoted 10 lines
mm/process_vm_access.c new file +3
-0+ +static ssize_t process_vm_rw_check_iovecs (pid_t pid, + const struct iovec
__user*lvec,(quoted diff) +2
-0+ unsigned long liovcnt, + const struct iovec
__user*rvec,(quoted diff) +2
-0+ unsigned long riovcnt, + unsigned long flags, int
vm_write)I'm allergic to functions with "check" in their name. Check for what?
Quoted 3 lines
And one would expect a
check_foo()to return a bool or an errno. This one returns assize_t! Weird! Interface documentation, please. Including return value semantics ;)
That part was split out from the main function because the iovec checks are different for 32 bit compatibility. Have renamed:
process_vm_rw -> process_vm_rw_core process_vm_rw_check_iovecs -> process_vm_rw compat_process_vm_rw_check_iovecs -> compat_process_vm_rw
...and added more doco - with return value semantics :-)
Chris
Signature · 1 line
[email protected]
Re: Cross Memory Attach v3 (includes updated patch based on v4)
In reply to Andrew MortonQuoted 48 lines · On Thu, 21 Jul 2011 15:09:08 -0700 Andrew Morton <[email protected]>…
Quoted 45 lines · On Tue, 19 Jul 2011 00:35:37 +0930 Christopher Yeoh <[email protected]> wrote:
(quoted diff) +21
-0+ +static ssize_t process_vm_rw(pid_t pid, const struct iovec *lvec, + unsigned long liovcnt, + const struct iovec *rvec, + unsigned long riovcnt, + unsigned long flags, int vm_write) +{ + struct task_struct *task; + struct page **process_pages = NULL; + struct mm_struct *mm; + unsigned long i; + ssize_t rc; + ssize_t bytes_copied; + unsigned long nr_pages = 0; + unsigned long nr_pages_iov; + unsigned long iov_l_curr_idx = 0; + size_t iov_l_curr_offset = 0; + ssize_t iov_len; + + /* + * Work out how many pages of struct pages we're going toneed
(quoted diff) +6
-0+ * when eventually calling get_user_pages + */ + for (i = 0; i < riovcnt; i++) { + iov_len = rvec[i].iov_len; + if (iov_len > 0) { + nr_pages_iov = ((unsignedlong)rvec[i].iov_base
(quoted diff) +2
-0+ + iov_len) + / PAGE_SIZE - (unsignedlong)rvec[i].iov_base
(quoted diff) +9
-0+ / PAGE_SIZE + 1; + nr_pages = max(nr_pages, nr_pages_iov); + } + } + + if (nr_pages == 0) + return 0; + + /* For reliability don't try to kmalloc more than 2 pagesworth */
(quoted diff) +1
-0+ process_pages = kmalloc(min_t(size_t,
PVM_MAX_KMALLOC_PAGES,(quoted diff) +1
-0+ sizeof(struct pages
Quoted 8 lines
Review
Quoted 2 lines
*)*nr_pages),
(quoted diff) +1
-0+ GFP_KERNEL);You might get some speed benefit by optimising for the small copies here. Define a local on-stack array of N page*'s and point
process_pagesat that if the number of pages is <= N. Saves a malloc/free and is more cache-friendly. But only if the result is measurable!
I have done some benchmarking on this, and it gains about 5-7% on a microbenchmark with 4kb size copies and about a 1% gain with a more realistic (but modified for smaller copies) hpcc benchmark. The performance gain disappears into the noise by about 64kb sized copies. No measurable overhead for larger copies. So I think its worth including
Included below is the patch (based on v4) - for ease of review the first diff is just against the latest version of CMA which has been posted here previously. The second is the entire CMA patch.
--- process_vm_access.c | 25 +++++++++++++++++-------- 1 file changed, 17 insertions(+), 8 deletions(-)
mm/process_vm_access.c +17 -8
@@ -221,6 +221,10 @@ static int process_vm_rw_single_vec(unsigned long addr,return rc; } +/* Maximum number of entries for process pages array +which lives on stack */ +#define PVM_MAX_PP_ARRAY_COUNT 16 +/** * process_vm_rw_core - core of reading/writing pages from task specified * @pid: PID of process to read/write from/to
@@ -241,7 +245,8 @@ static ssize_t process_vm_rw_core(pid_t pid, const struct iovec *lvec, unsigned long flags, int vm_write) {struct task_struct *task; -struct page **process_pages =NULL ; +struct page *pp_stack[PVM_MAX_PP_ARRAY_COUNT ]; +struct page **process_pages = pp_stack;struct mm_struct *mm;unsigned long i;ssize_t rc =0 ;
@@ -271,13 +276,16 @@ static ssize_t process_vm_rw_core(pid_t pid, const struct iovec *lvec,if (nr_pages ==0 )return 0 ; -/* For reliability don't try to kmalloc more than 2 pages worth */ - process_pages =kmalloc (min_t (size_t,PVM_MAX_KMALLOC_PAGES , -sizeof (struct pages *)*nr_pages), -GFP_KERNEL ); +if (nr_pages >PVM_MAX_PP_ARRAY_COUNT ) { +/* For reliability don't try to kmalloc more than +2 pages worth */ + process_pages =kmalloc (min_t (size_t,PVM_MAX_KMALLOC_PAGES , +sizeof (struct pages *)*nr_pages), +GFP_KERNEL ); -if (!process_pages) -return -ENOMEM ; +if (!process_pages) +return -ENOMEM ; + }/* Get process information */ rcu_read_lock ();
@@ -331,7 +339,8 @@ put_task_struct:put_task_struct (task); free_proc_pages: -kfree (process_pages); +if (process_pages != pp_stack) +kfree (process_pages);return rc; }
--- arch/powerpc/include/asm/systbl.h | 2 arch/powerpc/include/asm/unistd.h | 4 arch/x86/ia32/ia32entry.S | 2 arch/x86/include/asm/unistd_32.h | 4 arch/x86/include/asm/unistd_64.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 kernel/sys_ni.c | 4 mm/Makefile | 3 mm/process_vm_access.c | 496 +++++++++++++++++++++++++++++++++++++ security/keys/compat.c | 2 security/keys/keyctl.c | 2 17 files changed, 550 insertions(+), 17 deletions(-)
arch/powerpc/include/asm/systbl.h +2 -0
@@ -354,3 +354,5 @@ COMPAT_SYS_SPU(clock_adjtime) SYSCALL_SPU(syncfs) COMPAT_SYS_SPU(sendmmsg) SYSCALL_SPU(setns) +COMPAT_SYS(process_vm_readv) +COMPAT_SYS(process_vm_writev)
arch/powerpc/include/asm/unistd.h +3 -1
@@ -373,10 +373,12 @@#define __NR_syncfs 348#define __NR_sendmmsg 349#define __NR_setns 350 +#define __NR_process_vm_readv 351 +#define __NR_process_vm_writev 352#ifdef __KERNEL__ -#define __NR_syscalls 351 +#define __NR_syscalls 353#define __NR__exit __NR_exit#define NR_syscalls __NR_syscalls
arch/x86/ia32/ia32entry.S +2 -0
@@ -850,4 +850,6 @@ ia32_sys_call_table: .quad sys_syncfs .quad compat_sys_sendmmsg /* 345 */ .quad sys_setns + .quad compat_sys_process_vm_readv + .quad compat_sys_process_vm_writev ia32_syscall_end:
arch/x86/include/asm/unistd_32.h +3 -1
@@ -352,10 +352,12 @@#define __NR_syncfs 344#define __NR_sendmmsg 345#define __NR_setns 346 +#define __NR_process_vm_readv 347 +#define __NR_process_vm_writev 348#ifdef __KERNEL__ -#define NR_syscalls 347 +#define NR_syscalls 349#define __ARCH_WANT_IPC_PARSE_VERSION#define __ARCH_WANT_OLD_READDIR
arch/x86/include/asm/unistd_64.h +4 -0
@@ -681,6 +681,10 @@ __SYSCALL(__NR_syncfs, sys_syncfs) __SYSCALL(__NR_sendmmsg, sys_sendmmsg)#define __NR_setns 308 __SYSCALL(__NR_setns, sys_setns) +#define __NR_process_vm_readv 309 +__SYSCALL(__NR_process_vm_readv, sys_process_vm_readv) +#define __NR_process_vm_writev 310 +__SYSCALL(__NR_process_vm_writev, sys_process_vm_writev)#ifndef __NO_STUBS#define __ARCH_WANT_OLD_READDIR
arch/x86/kernel/syscall_table_32.S +2 -0
@@ -346,3 +346,5 @@ ENTRY(sys_call_table) .long sys_syncfs .long sys_sendmmsg /* 345 */ .long sys_setns + .long sys_process_vm_readv + .long sys_process_vm_writev
fs/aio.c +2 -2
@@ -1387,13 +1387,13 @@ static ssize_t aio_setup_vectored_rw(int type, struct kiocb *kiocb, bool compat) ret =compat_rw_copy_check_uvector (type, (struct compat_iovec __user *)kiocb->ki_buf, kiocb->ki_nbytes,1 , &kiocb->ki_inline_vec, - &kiocb->ki_iovec); + &kiocb->ki_iovec,1 ); else#endif ret =rw_copy_check_uvector (type, (struct iovec __user *)kiocb->ki_buf, kiocb->ki_nbytes,1 , &kiocb->ki_inline_vec, - &kiocb->ki_iovec); + &kiocb->ki_iovec,1 );if (ret <0 ) goto out;
fs/compat.c +4 -3
@@ -550,7 +550,7 @@ out:ssize_t compat_rw_copy_check_uvector (int type,const struct compat_iovec __user *uvector,unsigned long nr_segs,unsigned long fast_segs,struct iovec *fast_pointer, -struct iovec **ret_pointer) +struct iovec **ret_pointer,int check_access) {compat_ssize_t tot_len;struct iovec *iov = *ret_pointer = fast_pointer;
@@ -597,7 +597,8 @@ ssize_t compat_rw_copy_check_uvector(int type, }if (len <0 )/* size_t not fitting in compat_ssize_t .. */ goto out; -if (!access_ok (vrfy_dir (type),compat_ptr (buf), len)) { +if (check_access && + !access_ok (vrfy_dir (type),compat_ptr (buf), len)) { ret = -EFAULT ; goto out; }
@@ -1111,7 +1112,7 @@ static ssize_t compat_do_readv_writev(int type, struct file *file, goto out; tot_len =compat_rw_copy_check_uvector (type, uvector, nr_segs, -UIO_FASTIOV , iovstack, &iov); +UIO_FASTIOV , iovstack, &iov,1 );if (tot_len ==0 ) { ret =0 ; goto out;
fs/read_write.c +5 -3
@@ -575,7 +575,8 @@ ssize_t do_loop_readv_writev(struct file *filp, struct iovec *iov,ssize_t rw_copy_check_uvector (int type,const struct iovec __user * uvector,unsigned long nr_segs,unsigned long fast_segs,struct iovec *fast_pointer, -struct iovec **ret_pointer) +struct iovec **ret_pointer, +int check_access) {unsigned long seg;ssize_t ret;
@@ -631,7 +632,8 @@ ssize_t rw_copy_check_uvector(int type, const struct iovec __user * uvector, ret = -EINVAL ; goto out; } -if (unlikely (!access_ok (vrfy_dir (type), buf, len))) { +if (check_access + &&unlikely (!access_ok (vrfy_dir (type), buf, len))) { ret = -EFAULT ; goto out; }
@@ -663,7 +665,7 @@ static ssize_t do_readv_writev(int type, struct file *file, } ret =rw_copy_check_uvector (type, uvector, nr_segs, -ARRAY_SIZE (iovstack), iovstack, &iov); +ARRAY_SIZE (iovstack), iovstack, &iov,1 );if (ret <=0 ) goto out;
include/linux/compat.h +2 -1
@@ -557,7 +557,8 @@ extern ssize_t compat_rw_copy_check_uvector(int type,const struct compat_iovec __user *uvector, unsigned long nr_segs, unsigned long fast_segs, struct iovec *fast_pointer, - struct iovec **ret_pointer); + struct iovec **ret_pointer, + int check_access);extern void __user *compat_alloc_user_space (unsigned long len);
include/linux/fs.h +4 -3
@@ -1608,9 +1608,10 @@ struct inode_operations {struct seq_file ;ssize_t rw_copy_check_uvector (int type,const struct iovec __user * uvector, -unsigned long nr_segs,unsigned long fast_segs, -struct iovec *fast_pointer, -struct iovec **ret_pointer); +unsigned long nr_segs,unsigned long fast_segs, +struct iovec *fast_pointer, +struct iovec **ret_pointer, +int check_access);extern ssize_t vfs_read (struct file *,char __user *,size_t ,loff_t *);extern ssize_t vfs_write (struct file *,const char __user *,size_t ,loff_t *);
include/linux/syscalls.h +13 -0
@@ -847,4 +847,17 @@ asmlinkage long sys_open_by_handle_at(int mountdirfd,struct file_handle __user *handle, int flags);asmlinkage long sys_setns (int fd,int nstype); +asmlinkage long sys_process_vm_readv (pid_t pid, +const struct iovec __user *lvec, +unsigned long liovcnt, +const struct iovec __user *rvec, +unsigned long riovcnt, +unsigned long flags); +asmlinkage long sys_process_vm_writev (pid_t pid, +const struct iovec __user *lvec, +unsigned long liovcnt, +const struct iovec __user *rvec, +unsigned long riovcnt, +unsigned long flags); +#endif
kernel/sys_ni.c +4 -0
@@ -146,6 +146,10 @@ cond_syscall(sys_io_submit);cond_syscall (sys_io_cancel);cond_syscall (sys_io_getevents);cond_syscall (sys_syslog); +cond_syscall (sys_process_vm_readv); +cond_syscall (sys_process_vm_writev); +cond_syscall (compat_sys_process_vm_readv); +cond_syscall (compat_sys_process_vm_writev);/* arch-specific weak syscall entries */ cond_syscall (sys_pciconfig_read);
mm/Makefile +2 -1
@@ -5,7 +5,8 @@ mmu-y := nommu.o mmu-$(CONFIG_MMU) := fremap.o highmem.o madvise.o memory.o mincore.o \ mlock.o mmap.o mprotect.o mremap.o msync.o rmap.o \ - vmalloc.o pagewalk.o pgtable-generic.o + vmalloc.o pagewalk.o pgtable-generic.o \ + process_vm_access.o obj-y := filemap.o mempool.o oom_kill.o fadvise.o \ maccess.o page_alloc.o page-writeback.o \
mm/process_vm_access.c new file +496 -0
496 lines not on this page · raw message
security/keys/compat.c +1 -1
@@ -38,7 +38,7 @@ long compat_keyctl_instantiate_key_iov( ret =compat_rw_copy_check_uvector (WRITE , _payload_iov, ioc,ARRAY_SIZE (iovstack), - iovstack, &iov); + iovstack, &iov,1 );if (ret <0 )return ret;if (ret ==0 )
security/keys/keyctl.c +1 -1
@@ -1065,7 +1065,7 @@ long keyctl_instantiate_key_iov(key_serial_t id, goto no_payload; ret =rw_copy_check_uvector (WRITE , _payload_iov, ioc, -ARRAY_SIZE (iovstack), iovstack, &iov); +ARRAY_SIZE (iovstack), iovstack, &iov,1 );if (ret <0 )return ret;if (ret ==0 )
Signature · 8 lines
[email protected] -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM, see: http://www.linux-mm.org/ . Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/ Don't email: <a href=mailto:"[email protected]"> [email protected] </a>
Hi Christopher,
Quoted 2 lines · Christopher Yeoh
For arch maintainers there are some simple tests to be able to quickly verify that the syscalls are working correctly here:
I'm wiring up these new syscalls on m68k.
Quoted 1 line
The included README talks about:
setup_process_readv_simple
setup_process_readv_iovec
setup_process_writev
while the actual test executables are called:
setup_process_vm_readv_simple
setup_process_vm_readv_iovec
setup_process_vm_writev
On m68k (ARAnyM), the first and third test succeed. The second one fails, though:
# Setting up target with num iovecs 10, test buffer size 100000 Target process is setup
Run the following to test:
./t_process_vm_readv_iovec 1574 10 0x800030b0 89 0x80003110 38302 0x8000c6b8 22423 0x80011e58 18864 0x80016810 583 0x80016a60 8054 0x800189e0 3417 0x80019740 368 0x800198b8 897 0x80019c40 7003
and in the other window:
# ./t_process_vm_readv_iovec 1574 10 0x800030b0 89 0x80003110 38302 0x8000c6b8 22423 0x80011e58 18864 0x80016810 583 0x80016a60 8054 0x800189e0 3417 0x80019740 368 0x800198b8 897 0x80019c40 7003 copy_from_process failed: Invalid argument error code: 29 #
Any suggestions?
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- [email protected]
In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds
Hi Geert,
Quoted 15 lines · On Sun, 20 Nov 2011 11:16:17 +0100 Geert Uytterhoeven <[email protected]>…
Quoted 2 lines · Christopher Yeoh
For arch maintainers there are some simple tests to be able to quickly verify that the syscalls are working correctly here:
I'm wiring up these new syscalls on m68k.
Quoted 1 line
The included README talks about:
setup_process_readv_simple
setup_process_readv_iovec
setup_process_writev
Quoted 5 lines
while the actual test executables are called:
setup_process_vm_readv_simple
setup_process_vm_readv_iovec
setup_process_vm_writev
Oops. Have fixed this and uploaded a new version
http://ozlabs.org/~cyeoh/cma/cma-test-20111121.tgz
It also includes another minor change (see below)
Quoted 10 lines
On m68k (ARAnyM), the first and third test succeed. The second one fails, though:
# Setting up target with num iovecs 10, test buffer size 100000 Target process is setup
Run the following to test:
./t_process_vm_readv_iovec 1574 100x800030b0890x80003110383020x8000c6b8224230x80011e58188640x800168105830x80016a6080540x800189e034170x800197403680x800198b88970x80019c407003
Quoted 6 lines
and in the other window:
# ./t_process_vm_readv_iovec 1574 10 0x800030b0 89 0x80003110 38302 0x8000c6b8 22423 0x80011e58 18864 0x80016810 583 0x80016a60 8054 0x800189e0 3417 0x80019740 368 0x800198b8 897 0x80019c40 7003 copy_from_process failed: Invalid argument
That should say process_vm_readv instead of copy_from_process. The error message is fixed in the just updated test.
Quoted 5 lines
error code: 29
#Any suggestions?
Given that the first and third tests succeed, I think the problem is with the iovec parameters. The -EINVAL is most likely coming from rw_copy_check_uvector. Any chance that something bad is happening to lvec/liovcnt or rvec/riovcnt in the wireup?
The iovecs are checked in process_vm_rw before the core of the process_vm_readv/writev code is called so should be easy to confirm if this is the problem.
The other couple of places where it could possibly come from is that for some reason the flags parameter ends up being non zero or when looking up the task the mm is NULL. But given that the first and second tests succeed I think its unlikely that either of these is the cause.
Regards,
Chris
Signature · 8 lines
[email protected] -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM, see: http://www.linux-mm.org/ . Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/ Don't email: <a href=mailto:"[email protected]"> [email protected] </a>
Hi Christopher,
Quoted 39 lines · Christopher Yeoh
Quoted 17 lines · On Sun, 20 Nov 2011 11:16:17 +0100 Geert Uytterhoeven <[email protected]>…
Quoted 2 lines · Christopher Yeoh
For arch maintainers there are some simple tests to be able to quickly verify that the syscalls are working correctly here:
I'm wiring up these new syscalls on m68k.
On m68k (ARAnyM), the first and third test succeed. The second one fails, though:
# Setting up target with num iovecs 10, test buffer size 100000 Target process is setup
Run the following to test:
./t_process_vm_readv_iovec 1574 100x800030b0890x80003110383020x8000c6b8224230x80011e58188640x800168105830x80016a6080540x800189e034170x800197403680x800198b88970x80019c407003Quoted 6 lines
and in the other window:
# ./t_process_vm_readv_iovec 1574 10 0x800030b0 89 0x80003110 38302 0x8000c6b8 22423 0x80011e58 18864 0x80016810 583 0x80016a60 8054 0x800189e0 3417 0x80019740 368 0x800198b8 897 0x80019c40 7003 copy_from_process failed: Invalid argumentThat should say
process_vm_readvinstead ofcopy_from_process. The error message is fixed in the just updated test.Quoted 4 lines
error code: 29
#Any suggestions?
Given that the first and third tests succeed, I think the problem is with the iovec parameters. The
-EINVALis most likely coming fromrw_copy_check_uvector. Any chance that something bad is happening to lvec/liovcnt or rvec/riovcnt in the wireup?
Quoted 8 lines
The iovecs are checked in
process_vm_rwbefore the core of the process_vm_readv/writev code is called so should be easy to confirm if this is the problem.The other couple of places where it could possibly come from is that for some reason the flags parameter ends up being non zero or when looking up the task the mm is NULL. But given that the first and second tests succeed I think its unlikely that either of these is the cause.
It turned out the flags parameter was non-zero, due to syscall() only supporting up to 5 parameters in the glibc I was using for testing.
I checked the eglibc sources (2.11.1-0ubuntu7.8), and it's still not fixed there,
although I could find a fix for a similar issue in klibc
(http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=334917).
When forcing flags to zero, it works ;-)
So sorry for bothering you.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- [email protected]
In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds
Geert Uytterhoeven dixit:
Quoted 7 lines
It turned out the flags parameter was non-zero, due to
syscall()only supporting up to 5 parameters in the glibc I was using for testing.I checked the eglibc sources (2.11.1-0ubuntu7.8), and it's still not fixed there,
although I could find a fix for a similar issue in klibc
(http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=334917).
Does this work for you?
ports/sysdeps/unix/sysv/linux/m68k/syscall.S +2 -2
@@ -24,9 +24,9 @@ .text ENTRY (syscall) move.l 4(%sp), %d0 /* Load syscall number. */ - _DOARGS_5 (24) /* Frob arguments. */ + _DOARGS_6 (28) /* Frob arguments. */ trap &0 /* Do the system call. */ - UNDOARGS_5 /* Unfrob arguments. */ + UNDOARGS_6 /* Unfrob arguments. */ cmp.l &-4095, %d0 /* Check %d0 for error. */ jcc SYSCALL_ERROR_LABEL /* Jump to error handler if negative. */ rts /* Return to caller. */
bye,
//mirabilos
Signature · 3 lines
“Having a smoking section in a restaurant is like having
a peeing section in a swimming pool.”
-- Edward BurrHi Thorsten,
Quoted 10 lines · Thorsten Glaser
Geert Uytterhoeven dixit:
Quoted 7 lines
It turned out the flags parameter was non-zero, due to
syscall()only supporting up to 5 parameters in the glibc I was using for testing.I checked the eglibc sources (2.11.1-0ubuntu7.8), and it's still not fixed there,
although I could find a fix for a similar issue in klibc
(http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=334917).Does this work for you?
Thanks!
Your patch looks fine, but I'm not gonna compile eglibc now.
Quoted 8 lines
Index:
eglibc-2.13/ports/sysdeps/unix/sysv/linux/m68k/syscall.S
===================================================================ports/sysdeps/unix/sysv/linux/m68k/syscall.S 2011-12-04 14:36:26.000000000 +0000 renamed from ports/sysdeps/unix/sysv/linux/m68k/syscall.S 2011-12-04 14:36:16.000000000 +0000 +0
-0@@ -24,9 +24,9 @@.text
ENTRY (syscall)
move.l 4(%sp), %d0 /* Load syscall number. */
Quoted 8 lines
-
_DOARGS_5(24) /* Frob arguments. */
+_DOARGS_6(28) /* Frob arguments. */
trap &0 /* Do the system call. */
-UNDOARGS_5/* Unfrob arguments. */
+UNDOARGS_6/* Unfrob arguments. */ cmp.l &-4095, %d0 /* Check %d0 for error. */ jccSYSCALL_ERROR_LABEL/* Jump to error handler if negative. */ rts /* Return to caller. */
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- [email protected]
In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds
Quoted 6 lines · Thorsten Glaser
Index:
eglibc-2.13/ports/sysdeps/unix/sysv/linux/m68k/syscall.S
===================================================================ports/sysdeps/unix/sysv/linux/m68k/syscall.S +0
-0@@ -24,9 +24,9 @@ .text
ports/sysdeps/unix/sysv/linux/m68k/syscall.S line 32
Quoted 10 lines
ports/sysdeps/unix/sysv/linux/m68k/syscall.S +2
-2ENTRY (syscall) move.l 4(%sp), %d0 /* Load syscall number. */ - _DOARGS_5 (24) /* Frob arguments. */ + _DOARGS_6 (28) /* Frob arguments. */ trap &0 /* Do the system call. */ - UNDOARGS_5 /* Unfrob arguments. */ + UNDOARGS_6 /* Unfrob arguments. */ cmp.l &-4095, %d0 /* Check %d0 for error. */ jcc SYSCALL_ERROR_LABEL /* Jump to error handler if negative. */ rts /* Return to caller. */
Thanks, installed.
Andreas.
Signature · 3 lines
Andreas Schwab, [email protected] GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5 "And now for something completely different."
Andreas Schwab dixit:
Quoted 12 lines
Quoted 10 lines · Thorsten Glaser
Index:
eglibc-2.13/ports/sysdeps/unix/sysv/linux/m68k/syscall.S
===================================================================ports/sysdeps/unix/sysv/linux/m68k/syscall.S +1
-1@@ -24,9 +24,9 @@ .text ENTRY (syscall) move.l 4(%sp), %d0 /* Load syscall number. */ - _DOARGS_5 (24) /* Frob arguments. */ + _DOARGS_6 (28) /* Frob arguments. */
Quoted 8 lines
ports/sysdeps/unix/sysv/linux/m68k/syscall.S line 32
Quoted 6 lines
ports/sysdeps/unix/sysv/linux/m68k/syscall.S +1
-1trap &0 /* Do the system call. */ - UNDOARGS_5 /* Unfrob arguments. */ + UNDOARGS_6 /* Unfrob arguments. */ cmp.l &-4095, %d0 /* Check %d0 for error. */ jcc SYSCALL_ERROR_LABEL /* Jump to error handler if negative. */ rts /* Return to caller. */Thanks, installed.
(Where?) So, should $someone submit that to eglibc-ports and Debisn src:eglibc? Did it indeed do the trick?
bye,
//mirabilos
Signature · 3 lines
“Having a smoking section in a restaurant is like having
a peeing section in a swimming pool.”
-- Edward BurrQuoted 23 lines · Thorsten Glaser
Andreas Schwab dixit:
Quoted 12 lines
Quoted 10 lines · Thorsten Glaser
Index:
eglibc-2.13/ports/sysdeps/unix/sysv/linux/m68k/syscall.S
===================================================================ports/sysdeps/unix/sysv/linux/m68k/syscall.S +1
-1@@ -24,9 +24,9 @@ .text ENTRY (syscall) move.l 4(%sp), %d0 /* Load syscall number. */ - _DOARGS_5 (24) /* Frob arguments. */ + _DOARGS_6 (28) /* Frob arguments. */Quoted 8 lines
ports/sysdeps/unix/sysv/linux/m68k/syscall.S line 32
Quoted 6 lines
ports/sysdeps/unix/sysv/linux/m68k/syscall.S +1
-1trap &0 /* Do the system call. */ - UNDOARGS_5 /* Unfrob arguments. */ + UNDOARGS_6 /* Unfrob arguments. */ cmp.l &-4095, %d0 /* Check %d0 for error. */ jcc SYSCALL_ERROR_LABEL /* Jump to error handler if negative. */ rts /* Return to caller. */Thanks, installed.
Quoted 3 lines
(Where?) So, should $someone submit that to eglibc-ports and Debisn src:eglibc? Did it indeed do the trick?
This patch should be reported to [email protected]. If it also needs to be applied to the Debian package quickly, please open a bug report in the Debian BTS.
Signature · 2 lines
Aurelien Jarno GPG: 1024D/F1BCDB73 [email protected] http://www.aurel32.net
I’ve tested the below patch locally in the meantime, and it does not break anything.
Aurelien Jarno dixit:
Quoted 24 lines · Thorsten Glaser
Quoted 23 lines
Andreas Schwab dixit:
Quoted 20 lines
Quoted 6 lines · Thorsten Glaser
Index:
eglibc-2.13/ports/sysdeps/unix/sysv/linux/m68k/syscall.S
===================================================================ports/sysdeps/unix/sysv/linux/m68k/syscall.S +0
-0@@ -24,9 +24,9 @@ .textports/sysdeps/unix/sysv/linux/m68k/syscall.S line 32
Quoted 10 lines
ports/sysdeps/unix/sysv/linux/m68k/syscall.S +2
-2ENTRY (syscall) move.l 4(%sp), %d0 /* Load syscall number. */ - _DOARGS_5 (24) /* Frob arguments. */ + _DOARGS_6 (28) /* Frob arguments. */ trap &0 /* Do the system call. */ - UNDOARGS_5 /* Unfrob arguments. */ + UNDOARGS_6 /* Unfrob arguments. */ cmp.l &-4095, %d0 /* Check %d0 for error. */ jcc SYSCALL_ERROR_LABEL /* Jump to error handler if negative. */ rts /* Return to caller. */Thanks, installed.
Quoted 4 lines
Quoted 2 lines
(Where?) So, should $someone submit that to eglibc-ports and Debisn src:eglibc? Did it indeed do the trick?
This patch should be reported to [email protected]. If it also
Reporting hereby.
Quoted 2 lines
needs to be applied to the Debian package quickly, please open a bug report in the Debian BTS.
@kernel people, is this needed / useful? Do we want/need this? (I wonder why it's not using _DOARGS_6 already, as that looks as if it were designed for it.)
bye,
//mirabilos
Signature · 4 lines
22:20⎜<asarch> The crazy that persists in his craziness becomes a master 22:21⎜<asarch> And the distance between the craziness and geniality is only measured by the success 18:35⎜<asarch> "Psychotics are consistently inconsistent. The essence of sanity is to be inconsistently inconsistent