[Bug tapsets/11263] exposing foo32 syscalls

[mjw at redhat dot com]

------- Additional Comments From mjw at redhat dot com  2010-02-14 10:44 -------
Another wrinkle since 2.6.33:


commit f8b7256096a20436f6d0926747e3ac3d64c81d24
Author: Al Viro <viro@zeniv.linux.org.uk>
Date:   Mon Nov 30 17:37:04 2009 -0500

    Unify sys_mmap*
    
    New helper - sys_mmap_pgoff(); switch syscalls to using it.
    
    Acked-by: David S. Miller <davem@davemloft.net>
    Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>

This means everything is gated through sys_mmap_pgoff now on both x86_64 and
i386. But that also makes it hard to distinguish syscall.mmap (what we call
sys_mmap on x86_64) and syscall.mmap2 (what we call sys32_mmap on i386). I don't
immediately see how we can keep providing syscall.mmap2 without also triggering
syscall.mmap for the user.

-- 


http://sourceware.org/bugzilla/show_bug.cgi?id=11263

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.