When options inet6 is set in /etc/resolv.conf i'm getting buffer overflow while invoking spammassasin -r: # spamassassin -r <q1MvnXH-101060 *** buffer overflow detected ***: /usr/bin/perl terminated ======= Backtrace: ========= /lib/libc.so.6(__fortify_fail+0x50)[0xa593afc0] [...] Complete log is in attachment. Spamassasin is compiled with ipv6 support: mail-filter/spamassassin-3.2.5 USE="berkdb ipv6 postgres sqlite ssl tools -doc -ldap -mysql -qmail" Reproducible: Always Steps to Reproduce: 1.echo "options inet6" >> /etc/resolv.conf 2.spamassassin -r <some_mail 3.
Created attachment 206416 [details] spamassassin log
Created attachment 206418 [details] emerge --info
This problem is old.. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=405694
What version of dev-perl/IO-Socket-INET6 do you have installed?
I've installed dev-perl/IO-Socket-INET6-2.51 .
Now, i can't reproduce error. I don't know wich upgrade solved problem. Now i've got: glibc-2.10.1-r1 , spamassassin-3.2.5-r2 , IO-Socket-INET6-2.51 . So i'm closing this bug. (Is resolution "fixed" correct one? Problem dissappears without founding a reason.)
(In reply to comment #6) > Now, i can't reproduce error. I don't know wich upgrade solved problem. Now > i've got: glibc-2.10.1-r1 , spamassassin-3.2.5-r2 , IO-Socket-INET6-2.51 . So > i'm closing this bug. (Is resolution "fixed" correct one? Problem dissappears > without founding a reason.) > Thanks for providing further feedback. Technically, "WORKSFORME" would be the resolution, but it really doesn't matter, imo. :)
I'm sorry, but i have to reopen bug :( Yesterday i've added "options inet6" to resolv.conf, today i've found few messages in syslog: 2010-01-16T11:44:42.355423+01:00 localhost *** buffer overflow detected ***: perl - terminated 2010-01-16T11:44:42.355503+01:00 localhost perl: buffer overflow attack in function <unknown> - terminated 2010-01-16T11:44:42.355525+01:00 localhost Report to http://bugs.gentoo.org/ I still don't know what special case must happend to trigger this error. Problem doesn't appear on every mail (which is sended from exim to spamd through tcp connection). I'll try to found how to reproduce this error. IMHO this bug isn't so important to block STABLREQ.
Segfault appears when mail shoud be reported to SpamCop (no matter if SA is invoked as "spamassassin -r" or it is done by spamd process). I suppose the problem is in function reporting spam to SpamCop.
Marcin, can we close the bug so STABLEREQ bug 301125 can proceed?
As i said at #8 , go ahead.