From owner-freebsd-current@FreeBSD.ORG Thu Apr 19 23:23:35 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 239E216A406 for ; Thu, 19 Apr 2007 23:23:35 +0000 (UTC) (envelope-from citrin@citrin.ru) Received: from mail.classis.ru (classis.ru [213.248.60.120]) by mx1.freebsd.org (Postfix) with ESMTP id D574A13C44C for ; Thu, 19 Apr 2007 23:23:34 +0000 (UTC) (envelope-from citrin@citrin.ru) Received: from CITRIN (ppp85-140-127-113.pppoe.mtu-net.ru [85.140.127.113]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: citrin.citrin.ru) by mail.classis.ru (Postfix) with ESMTP id AE2781227BFA; Fri, 20 Apr 2007 03:23:33 +0400 (MSD) Date: Fri, 20 Apr 2007 03:22:26 +0400 From: Anton Yuzhaninov X-Mailer: The Bat! (v3.62.14) Professional Organization: Rambler X-Priority: 3 (Normal) Message-ID: <334983330.20070420032226@citrin.ru> To: Kris Kennaway In-Reply-To: <20070419223903.GA87190@xor.obsecurity.org> References: <313993633.20070419232238@citrin.ru> <4627DD1B.2080806@freebsd.org> <144280354.20070420023353@citrin.ru> <20070419223903.GA87190@xor.obsecurity.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Cc: freebsd-current@freebsd.org Subject: Re[2]: 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:23:35 -0000 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: >>=20 >> JE> Anton Yuzhaninov wrote: >> >> I try to test clamav 0.90.2 on current and got strange errors: >> >>=20 >> >> LibClamAV Warning: Multipart/alternative MIME message contains no bou= ndary header >> >> LibClamAV Warning: Multipart/ZZZZZZZZZZZZ?????? MIME message contains= no boundary header >> >> LibClamAV Warning: Multipart/related MIME message contains no boundar= y header >> >>=20 >> >> And sometimes clamd segfaults. >> >>=20 >> >> This Warnings issued randomly and it looks like race condition. >> >>=20 >> >> This problem occurred only when running two or more clamdscan >> >> processes in parallel. With one process no warnings on same test >> JE> ^^^^^^^^^ >> >> messages. >>=20 >> JE> Processes, not threads? If so, there's really no way malloc can be = to >> JE> blame for a race condition. >>=20 >> problem in clamd - it is multithread application. >>=20 >> 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. --=20 Anton Yuzhaninov.