On Sun, Nov 17, 2013 at 09:41:03PM +0100, Samuel Thibault wrote:
> Richard Braun, le Sun 17 Nov 2013 17:13:23 +0100, a écrit :
> > This patch makes use of a new GNU Mach specific call
> > (thread_terminate_release [1]) so that threads do terminate themselves
> > and release their stack, and in addi
All applied, thanks!
Samuel
Hello,
Richard Braun, le Sun 17 Nov 2013 17:13:23 +0100, a écrit :
> This patch makes use of a new GNU Mach specific call
> (thread_terminate_release [1]) so that threads do terminate themselves
> and release their stack, and in addition their last self reference,
> and their reply port.
I was fi
The following changes actually apply to Debian eglibc 2.17-96 sources,
and aren't meant to be pushed as such, but rather to review the various
solutions added to support thread termination.
The current state is to never terminate threads, on the assumption that
they can't both terminate and releas
Marin Ramesa, le Sun 17 Nov 2013 07:01:24 +0100, a écrit :
> These two are preliminary patches generated from dereference of null
> pointer reports. Let's see how this goes. If I got it right, I'll
> continue to work on this. If I got it wrong, I'll let someone more
> experienced deal with these ki
Marin Ramesa, le Sun 17 Nov 2013 07:01:26 +0100, a écrit :
> When fp_thread is not NULL and is not the current thread, and fp_save() does
> not alter the machine state, check if ifps is NULL before setting fp_valid
> to avoid dereference of null pointer.
A thread can not be stored in fp_thread bu
Marin Ramesa, le Sun 17 Nov 2013 07:01:25 +0100, a écrit :
> When ldt equals zero, and default branch is taken from the switch
> statement, and sel is not equal to zero, comparison results in
> a dereference of a null pointer. Avoid this.
>
> * i386/i386/user_ldt.c (ldt): Check if it equals zero.
