This is the mail archive of the mailing list for the glibc project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug malloc/25223] consider using Hardened Malloc

Adhemerval Zanella <adhemerval.zanella at linaro dot org> changed:

           What    |Removed                     |Added
                 CC|                            |adhemerval.zanella at linaro dot o
                   |                            |rg

--- Comment #1 from Adhemerval Zanella <adhemerval.zanella at linaro dot org> ---
Which is the exact idea of this enhancement request? GLIBC already has support
for interposable malloc, so the usage of an external interposable malloc is

If the idea is *replace* current malloc implementation I think a better
strategy would bring this up to libc-alpha instead of opening a bug report.
This is a huge task, that would require to take into consideration multiple
factors, and it will require much discussion. 

Also, the malloc implementation has been improved both in security, (for
instance 5b06f538c5, c0e82f11735, ebe544bf6e8e), usability and performance (the
tache support for instance). So I would prefer to work by identifying issues
with the current implementation and work towards fixing them while taking into
consideration not only security but performance metrics as well (as we have
done in the past).

You are receiving this mail because:
You are on the CC list for the bug.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]