Date: Thu, 19 Apr 2007 18:39:03 -0400 From: Kris Kennaway <kris@obsecurity.org> To: Anton Yuzhaninov <citrin@citrin.ru> Cc: freebsd-current@freebsd.org, Jason Evans <jasone@freebsd.org> Subject: Re: clamd memory corruption (may be jemalloc related) Message-ID: <20070419223903.GA87190@xor.obsecurity.org> In-Reply-To: <144280354.20070420023353@citrin.ru> References: <313993633.20070419232238@citrin.ru> <4627DD1B.2080806@freebsd.org> <144280354.20070420023353@citrin.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
--T4sUOijqQbZv57TR Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Apr 20, 2007 at 02:33:53AM +0400, Anton Yuzhaninov wrote: > Hello Jason, >=20 > 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 boun= dary header > >> LibClamAV Warning: Multipart/ZZZZZZZZZZZZ?????? MIME message contains = no boundary header > >> LibClamAV Warning: Multipart/related MIME message contains no boundary= 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. Note that jemalloc malloc debugging exposes different application bugs than phkmalloc did (due to technical differences). There were a number of such application bugs found during the initial testing, and (absent any direct evidence to the contrary) it is likely that this is another one. Kris --T4sUOijqQbZv57TR Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (FreeBSD) iD8DBQFGJ++GWry0BWjoQKURAsGlAJ9MWYJPq3ke1bOqp4/gOd/WgOC+7gCfTsz1 ERBZcZWS6rooqXXQsrE1OWw= =1XRr -----END PGP SIGNATURE----- --T4sUOijqQbZv57TR--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070419223903.GA87190>