This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: [RFC][PATCH 0/7] Additonal integrity checks for the malloc implementation
- From: Istvan Kurucsai <pistukem at gmail dot com>
- To: DJ Delorie <dj at redhat dot com>
- Cc: libc-alpha at sourceware dot org
- Date: Fri, 27 Oct 2017 16:42:35 +0200
- Subject: Re: [RFC][PATCH 0/7] Additonal integrity checks for the malloc implementation
- Authentication-results: sourceware.org; auth=none
- References: <1496220235-12750-1-git-send-email-pistukem@gmail.com> <xnefv3ea01.fsf@greed.delorie.com> <CAHJ3J3n3fd77q-7qTh2kw8BYuXz-yRQfB+nhe3vXk+5_GCGjVQ@mail.gmail.com> <CAHJ3J3kv_XCoKmye0dLcQcYxunaR0uCtp9hp+qStBJa0WSEGbw@mail.gmail.com>
The recent malloc hardening patches sent in just reminded me of these
which I completely forgot about. Should I resubmit them actualized for
the current state of the malloc code?
On Thu, Jun 8, 2017 at 9:20 PM, Istvan Kurucsai <pistukem@gmail.com> wrote:
> Quick update: I didn't find the time to do it this week and will be
> leaving for vacation, so the soonest I can look into adding tests will
> be two weeks from now.
>
> On Sat, Jun 3, 2017 at 10:43 AM, Istvan Kurucsai <pistukem@gmail.com> wrote:
>> They passed make check, I will look into adding tests next week. Yes,
>> I would need someone to check them in.
>>
>> Thanks.
>>
>> On Thu, Jun 1, 2017 at 10:19 PM, DJ Delorie <dj@redhat.com> wrote:
>>>
>>> These look good to me, assuming they've passed "make check". Could use
>>> test cases for the hackery we're trying to prevent, but that shouldn't
>>> stop the patches from going in.
>>>
>>> After you have consensus, will you need someone to check these in for
>>> you?