https://bugs.kde.org/show_bug.cgi?id=408414

Mark Wielaard <m...@klomp.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|CONFIRMED                   |RESOLVED
         Resolution|---                         |FIXED

--- Comment #8 from Mark Wielaard <m...@klomp.org> ---
(In reply to Alexandra Hajkova from comment #7)
> Created attachment 121289 [details]
> patch

This looks great. Thanks for the polish and wiring up the other arches.
I haven't been able to test them all. But the nightly builders will catch any
issues.
Pushed to valgrind git master as:

commit b0861063a8d2a55bb7423e90d26806bab0f78a12 (HEAD -> master, origin/master,
origin/HEAD)
Author: Alexandra Hájková <ahajk...@redhat.com>
Date:   Tue Jun 4 13:47:14 2019 +0200

    Add support for preadv2 and pwritev2 syscalls

    Support for amd64, x86 - 64 and 32 bit, arm64, ppc64, ppc64le,
    s390x, mips64. This should work identically on all
    arches, tested on x86 32bit and 64bit one, but enabled on all.

    Refactor the code to be reusable between old/new syscalls. Resolve TODO
    items in the code. Add the testcase for the preadv2/pwritev2 and also
    add the (similar) testcase for the older preadv/pwritev syscalls.

    Trying to test handling an uninitialized flag argument for the v2 syscalls
    does not work because the flag always comes out as defined zero.
    Turns out glibc does this deliberately on 64bit architectures because
    the kernel does actually have a low_offset and high_offset argument, but
    ignores the high_offset/assumes it is zero.
   
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=601cc11d054ae4b5e9b5babec3d8e4667a2cb9b5

    https://bugs.kde.org/408414

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to