Revert "Disable SafeStack for test that requires direct stack access"

SafeStack support has been abandoned.

Bug: 908597
Change-Id: If425e16a2bed5781d32a935e0dca06a4666fabc4
Reviewed-on: https://chromium-review.googlesource.com/c/1351751Reviewed-by: Lei Zhang <thestig@chromium.org>
Commit-Queue: Vlad Tsyrklevich <vtsyrklevich@chromium.org>
Cr-Commit-Position: refs/heads/master@{#611542}

base/debug/proc_maps_linux_unittest.cc

@@ -191,11 +191,6 @@ TEST(ProcMapsTest, Permissions) {
 // instrumentation for this function to force the variable to be local.
 __attribute__((no_sanitize_address))
 #endif
-#if HAS_FEATURE(safe_stack)
-// SafeStack places address-taken variables on the unsafe stack, but the default
-// stack region in /proc/self/maps is the safe stack.
-__attribute__((no_sanitize("safe-stack")))
-#endif
 void CheckProcMapsRegions(const std::vector<MappedMemoryRegion> &regions) {
   // We should be able to find both the current executable as well as the stack
   // mapped into memory. Use the address of |exe_path| as a way of finding the