On Mon, Oct 14, 2019 at 9:29 AM Jan Stancek <jstancek@xxxxxxxxxx> wrote: > > > > ----- Original Message ----- > > > > Hello, > > > > We ran automated tests on a recent commit from this kernel tree: > > > > Kernel repo: > > git://git.kernel.org/pub/scm/linux/kernel/git/sashal/linux-stable.git > > Commit: d6c2c23a29f4 - Merge branch 'stable-next' of > > ssh://chubbybox:/home/sasha/data/next into stable-next > > > > The results of these automated tests are provided below. > > > > Overall result: FAILED (see details below) > > Merge: OK > > Compile: OK > > Tests: FAILED > > > > All kernel binaries, config files, and logs are available for download here: > > > > https://artifacts.cki-project.org/pipelines/223563 > > > > One or more kernel tests failed: > > > > aarch64: > > ❌ LTP: openposix test suite > > > > Test [1] is passing value close to LONG_MAX, which on arm64 is now treated as tagged userspace ptr: > 057d3389108e ("mm: untag user pointers passed to memory syscalls") > > And now seems to hit overflow check after sign extension (EINVAL). > Test should probably find different way to choose invalid pointer. > > [1] https://github.com/linux-test-project/ltp/blob/master/testcases/open_posix_testsuite/conformance/interfaces/mlock/8-1.c +Catalin and Vincenzo Per Documentation/arm64/tagged-address-abi.rst we now have: User addresses not accessed by the kernel but used for address space management (e.g. ``mmap()``, ``mprotect()``, ``madvise()``). The use of valid tagged pointers in this context is always allowed. However this breaks the test above. What do you think we should do here?
