dev-libs/jemalloc: drop USE=hardened option

The only effect of USE=hardened was to pass a --disable-syscall
configure option. It's only effect is to use library wrappers
to memory allocation instead of direct syscalls to kernel.

As jemalloc overrides a bunch of library memory allocation
library calls itself this introduces extra chances to interact
badly with other tool that override library calls.

In #617518 sandbox became incompatible with jemalloc users and
produced deadlocks. Example from ruby[jemalloc]:

    malloc_init() [called by jemalloc]
     -> open("/proc/sys/vm/overcommit_memory")
      -> [sandbox takes over] open_DEFAULT()
       -> [sandbox initializes]
        -> init_env_entries ()
         -> _xmalloc()
          -> sb_mmap() [ try hard not to use olerloaded mmap() ]
           -> get_dlsym("mmap")
            -> calloc() [ sandbox loses control, overridden by jemalloc ]
             -> malloc_init() [ recursion, gets locked in attempt to
                  lock again locked malloc_init mutex ]

There should be no reason to use --disable-syscall on linux.
And especially not under generic (and enabled by default on
hardened profiles) USE=hardened.

The change drops --disable-syscall passing (and USE=hardened)
completely.

Users still can do it via EXTRA_ECONF= but there should be no
need for that. Upstream ./configure should do the right thing.

Reported-by: Maciej Piechotka
Closes: https://bugs.gentoo.org/617518
Package-Manager: Portage-3.0.17, Repoman-3.0.2
Signed-off-by: Sergei Trofimovich <slyfox@gentoo.org>

0 files changed, 0 insertions, 0 deletions