Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 20 Apr 2007 03:22:26 +0400
From:      Anton Yuzhaninov <citrin@citrin.ru>
To:        Kris Kennaway <kris@obsecurity.org>
Cc:        freebsd-current@freebsd.org
Subject:   Re[2]: clamd memory corruption (may be jemalloc related)
Message-ID:  <334983330.20070420032226@citrin.ru>
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>

next in thread | previous in thread | raw e-mail | index | archive | help
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.




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?334983330.20070420032226>