Milter-greylist

Francois Tigeot <ftigeot@...> wrote:

> parent (672792688) TSS key 0x0 set to 0xbfbff6c8
> parent (672792688) TSS key 0x0 readen as 0xbfbff6c8
> child (672792912) starts, key = 0x0
> child (672792912) TSS key 0x0 readen as 0x28083500

Ok, I think we tracked down the problem.

I am not a POSIX.1 expert, but I suspect this is a pthread bug. This TSS
has not been set in the child, so reading the key in the child should
fail. I just say I am suspicious, since it might be a grey area in the
specification, where both behavior are compliant to the letter of the
standard.

Example on NetBSD 5.0.2
parent (-1080033280) TSS key 0x0 set to 0xbfbfecd8
parent (-1080033280) TSS key 0x0 readen as 0xbfbfecd8
child (-1151336448) starts, key = 0x0
tss: pthread_getspecific() failed in child

On Linux 2.6.18
parent (16384) TSS key (nil) set to 0xbfa6dd34
parent (16384) TSS key (nil) readen as 0xbfa6dd34
child (16386) starts, key = (nil)
tss: pthread_getspecific() failed in child

On Darwin 8.11.0 (Mac OSX 10.4.11 PPC)
parent (-1610551928) TSS key 0x6 set to 0xbffffb9c
parent (-1610551928) TSS key 0x6 readen as 0xbffffb9c
child (25167360) starts, key = 0x6
tss: pthread_getspecific() failed in child

On Darwin 10.6.0 (Mac OSX 10.6 i386)
parent (1885527200) TSS key 0x101 set to 0x7fff5fbffc40
parent (1885527200) TSS key 0x101 readen as 0x7fff5fbffc40
child (745472) starts, key = 0x101
tss: pthread_getspecific() failed in child

(other mailing list subscriber are welcome to post results on other
systems).

Could you run the test on the previous DragonflyBSD release, which ran
milter-greylist fine? 

-- 
Emmanuel Dreyfus
http://hcpnet.free.fr/pubz
manu@...