rewrote changelogs (so they should be readable by humans also) rebase on linux-next-20170306 (minor: sysret_rip test added) O 5 is a selftest to check that 32-bit mmap() does return 32-bit To the bitness of executed binary, not of the syscall. O 4 fixes behavior of MAP_32BIT - at this moment it's related With MAP_FIXED for hiding that mapping from 32-bit address space. Than 4Gb in compat ELFs - that may be used when 4Gb is not enough or It also makes possible to allocate with 64-bit mmap() address higher Of launched binary's bitness (the same for 64-bit syscalls). Which makes the behavior of 32-bit syscalls the same independently Mmap base according to bitness of the syscall. Those bases are separated from 64-bit ones, which allows to use Mmap_compat_base and mmap_compat_legacy_base. O 3 fixes 32-bit syscall returning address over 4Gb in applications, O 1-2 are just preparation to introduce new mmap bases ![]() There are a couple of fixes related to x86 mmap(): With his set or help him with rebasing (if he need it). ![]() (with the patch "mm, x86: introduceĬonflicts are minor and I'm OK rather rebase this set on linux-next Note: this patches set has some minor conflicts with Kirill's Peter Anvin, Andy Lutomirski, Borislav Petkov, x86, linux-mm,Ĭyrill Gorcunov, Kirill A. Fix compatible mmap() return pointer over 4Gb All of help / color / mirror / Atom feed * Fix compatible mmap() return pointer over 4Gb 14:17 ` Dmitry Safonov 0 siblings, 0 replies 33+ messages in threadįrom: Dmitry Safonov 14:17 UTC ( / raw)Ĭc: 0x7f454c46, Dmitry Safonov, Thomas Gleixner, Ingo Molnar,
0 Comments
Leave a Reply. |