This is the mail archive of the libc-help@sourceware.org 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]

Re: Double free check in malloc.c for 64 bit architectures

From: Florian Weimer <fweimer at redhat dot com>
To: Claude Zou <claude dot zou dot work at gmail dot com>
Cc: libc-help at sourceware dot org
Date: Wed, 20 Nov 2019 20:26:21 +0100
Subject: Re: Double free check in malloc.c for 64 bit architectures
References: <CALCTegi8wO_exjSoGwQrXLwkU2c8_sAC+yRo9mws9ZMS_cuTkg@mail.gmail.com> <874kyzvspg.fsf@oldenburg2.str.redhat.com> <CALCTegimn_XJvos=JETvd3LX=+_Uk0HoVLR2ZX_DssOMznVVQw@mail.gmail.com>

* Claude Zou:

> Is there any particular reason such a check (such as the one currently
> in tcache) has not been done for fastbins yet?

I'm not aware of any particular reason.  The implementation would be
quite similar to the current tcache check—it should be safe to traverse
the list as long as the arena lock is acquired.  But the list is
potentially unbound, so it may make sense to consolidate the fastbin, or
at least its tail.

Thanks,
Florian

References:
- Double free check in malloc.c for 64 bit architectures
  - From: Claude Zou
- Re: Double free check in malloc.c for 64 bit architectures
  - From: Florian Weimer
- Re: Double free check in malloc.c for 64 bit architectures
  - From: Claude Zou

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