Re: clamd memory corruption (may be jemalloc related)

On Fri, Apr 20, 2007 at 03:22:26AM +0400, Anton Yuzhaninov wrote:
> Hello Kris,
> 
> You wrote on Friday, April 20, 2007, 2:39:03 AM:
> 
> KK> On Fri, Apr 20, 2007 at 02:33:53AM +0400, Anton Yuzhaninov wrote:
> >> Hello Jason,
> >>
> >> You wrote on Friday, April 20, 2007, 1:20:27 AM:
> >> 
> >> JE> Anton Yuzhaninov wrote:
> >> >> I try to test clamav 0.90.2 on current and got strange errors:
> >> >> 
> >> >> LibClamAV Warning: Multipart/alternative MIME message contains no boundary header
> >> >> LibClamAV Warning: Multipart/ZZZZZZZZZZZZ?????? MIME message contains no boundary header
> >> >> LibClamAV Warning: Multipart/related MIME message contains no boundary header
> >> >> 
> >> >> And sometimes clamd segfaults.
> >> >> 
> >> >> This Warnings issued randomly and it looks like race condition.
> >> >> 
> >> >> This problem occurred only when running two or more clamdscan
> >> >> processes in parallel. With one process no warnings on same test
> >> JE>    ^^^^^^^^^
> >> >> messages.
> >> 
> >> JE> Processes, not threads?  If so, there's really no way malloc can be to
> >> JE> blame for a race condition.
> >> 
> >> problem in clamd - it is multithread application.
> >> 
> >> clamdscan used only for load one or more thread in clamd.
> 
> KK> Note that jemalloc malloc debugging exposes different application bugs
> KK> than phkmalloc did (due to technical differences).  There were a
> KK> number of such application bugs found during the initial testing, and
> KK> (absent any direct evidence to the contrary) it is likely that this is
> KK> another one.
> 
> Clamav code quality is low, and probably it has bugs :(
> But not obvious how to find this bugs.

Turn off AJ then ;-)

Kris