From owner-freebsd-current@FreeBSD.ORG Thu Feb 9 21:55:51 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 993E416A420 for ; Thu, 9 Feb 2006 21:55:51 +0000 (GMT) (envelope-from pjd@garage.freebsd.pl) Received: from mail.garage.freebsd.pl (arm132.internetdsl.tpnet.pl [83.17.198.132]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0FCE643D6D for ; Thu, 9 Feb 2006 21:55:39 +0000 (GMT) (envelope-from pjd@garage.freebsd.pl) Received: by mail.garage.freebsd.pl (Postfix, from userid 65534) id 41DED50D3B; Thu, 9 Feb 2006 22:55:37 +0100 (CET) Received: from localhost (dlj105.neoplus.adsl.tpnet.pl [83.24.39.105]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.garage.freebsd.pl (Postfix) with ESMTP id C870A50B72; Thu, 9 Feb 2006 22:55:30 +0100 (CET) Date: Thu, 9 Feb 2006 22:55:14 +0100 From: Pawel Jakub Dawidek To: Steve Kargl Message-ID: <20060209215513.GA3590@garage.freebsd.pl> References: <20060207183152.GA50629@troutmask.apl.washington.edu> <20060207190121.GF19674@comp.chem.msu.su> <20060207191408.GA50909@troutmask.apl.washington.edu> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="pWyiEgJYm5f9v55/" Content-Disposition: inline In-Reply-To: <20060207191408.GA50909@troutmask.apl.washington.edu> X-PGP-Key-URL: http://people.freebsd.org/~pjd/pjd.asc X-OS: FreeBSD 7.0-CURRENT i386 User-Agent: mutt-ng/devel-r535 (FreeBSD) X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on mail.garage.freebsd.pl X-Spam-Level: X-Spam-Status: No, score=-0.5 required=3.0 tests=BAYES_00,RCVD_IN_NJABL_DUL, RCVD_IN_SORBS_DUL autolearn=no version=3.0.4 Cc: Yar Tikhiy , freebsd-current@freebsd.org Subject: Re: memguard monitoring of more than 1 memory_type? 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, 09 Feb 2006 21:55:51 -0000 --pWyiEgJYm5f9v55/ Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Feb 07, 2006 at 11:14:08AM -0800, Steve Kargl wrote: +> On Tue, Feb 07, 2006 at 10:01:21PM +0300, Yar Tikhiy wrote: +> > On Tue, Feb 07, 2006 at 10:31:52AM -0800, Steve Kargl wrote: +> > > Can memguard monitor the usage of more that one memory_type? +> >=20 +> > From the memguard(9) manpage: +> >=20 +> > Currently, MemGuard can only take over malloc(), realloc() and fr= ee() for +> > a particular malloc type. +>=20 +> Thanks for pointing out the obvious. I've read that manpage several +> times and somehow missed the word "particular". It's unfortunate +> that it can't monitor more than one type of memory allocation because +> the new pts code has either uncovered a latent bug in devfs or the +> pts patch is stomping on memory. It shouldn't be hard to implement. You need to change function memguard_cmp() in sys/vm/memguard.c, which decides which memory type should be monitored. --=20 Pawel Jakub Dawidek http://www.wheel.pl pjd@FreeBSD.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! --pWyiEgJYm5f9v55/ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFD67pBForvXbEpPzQRAr1GAKCiKlR/9iMRlgDnd5g3g5HlttVONwCgjkAY Y7ukj6N+jqSwEXo/0sm0Myk= =11Gg -----END PGP SIGNATURE----- --pWyiEgJYm5f9v55/--