From owner-freebsd-current@FreeBSD.ORG Thu Apr 19 23:27:52 2007 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id E4A5716A409 for ; Thu, 19 Apr 2007 23:27:52 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.freebsd.org (Postfix) with ESMTP id D4CCF13C483 for ; Thu, 19 Apr 2007 23:27:52 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 408CE1A4D80; Thu, 19 Apr 2007 16:28:10 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 178E451406; Thu, 19 Apr 2007 19:27:52 -0400 (EDT) Date: Thu, 19 Apr 2007 19:27:51 -0400 From: Kris Kennaway To: Anton Yuzhaninov Message-ID: <20070419232751.GA87857@xor.obsecurity.org> References: <313993633.20070419232238@citrin.ru> <4627DD1B.2080806@freebsd.org> <144280354.20070420023353@citrin.ru> <20070419223903.GA87190@xor.obsecurity.org> <334983330.20070420032226@citrin.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <334983330.20070420032226@citrin.ru> User-Agent: Mutt/1.4.2.2i Cc: freebsd-current@freebsd.org, Kris Kennaway Subject: Re: clamd memory corruption (may be jemalloc related) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 19 Apr 2007 23:27:53 -0000 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