Milter-greylist

On Sun, Jan 30, 2011 at 01:05:15PM +0100, manu@... wrote:
> 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
> 
> 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
> 
> Could you run the test on the previous DragonflyBSD release, which ran
> milter-greylist fine? 

DragonFly 2.6 give the same answers as most other systems:

parent (672727152) TSS key 0x0 set to 0xbfbffbc8
parent (672727152) TSS key 0x0 read as 0xbfbffbc8
child (672727376) starts, key = 0x0
tss: pthread_getspecific() failed in child

DragonFly 2.8 and 2.9  give these answers:

parent (5505216) TSS key 0x0 set to 0x7ffffffff1d0
parent (5505216) TSS key 0x0 read as 0x7ffffffff1d0
child (5505568) starts, key = 0x0
child (5505568) TSS key 0x0 read as 0x800533900
child (5505568) exit
parent (5505216) exit

I'll get in touch with the kernel guys to try to get this fixed.

-- 
Francois Tigeot