CI: Revert ARCH_MMAP_RND_BITS libasan workaround

This reverts commit 5713c2ffdd. This workaround is reportedly now applied in the base image.
Author: https://github.com/trflynn89 Commit: https://github.com/SerenityOS/serenity/commit/3b2f4a4041 Pull-request: https://github.com/SerenityOS/serenity/pull/23719 Issue: https://github.com/SerenityOS/serenity/issues/23571
2024-03-25 12:46:58 -04:00 · 2024-03-25 12:46:58 -04:00 · 3b2f4a4041 · 2024-07-18 03:20:18 +09:00
commit 3b2f4a4041
parent 7dd5457b8f
1 changed files with 0 additions and 9 deletions
--- a/Meta/Azure/Lagom.yml
+++ b/Meta/Azure/Lagom.yml
@ -58,15 +58,6 @@ jobs:
          ccache_version: 2
        serenity_ccache_size: '2G'

-    # On Ubuntu, with Linux kernel 6.5, ARCH_MMAP_RND_BITS was changed from ARCH_MMAP_RND_BITS_MIN (28 on x64) to
-    # ARCH_MMAP_RND_BITS_MAX (32 on x64). This breaks assumptions made by libasan's allocators, and we see a flaky
-    # crash from within libasan itself. Here, we restore the previous value until we have a version of GCC which fixes
-    # the issue in libasan (reportedly 13.2.1): https://stackoverflow.com/questions/77894856/possible-bug-in-gcc-sanitizers
-    - ${{ if eq(parameters.os, 'Linux') }}:
-      - script: |
-          sudo sysctl vm.mmap_rnd_bits=28
-        displayName: 'Work around libasan ASLR bug'
-
    - ${{ if eq(parameters.os, 'Android') }}:
      - script: |
          yes | $ANDROID_SDK_ROOT/tools/bin/sdkmanager "ndk;$(ndk_version)"