Date: Tue, 12 Sep 2006 10:47:47 +0200 From: "Attilio Rao" <attilio@freebsd.org> To: "Alexander Leidinger" <netchild@freebsd.org> Cc: perforce@freebsd.org, John Baldwin <jhb@freebsd.org>, mag@intron.ac Subject: Re: PERFORCE change 105930 for review Message-ID: <3bbf2fe10609120147p343f48a4yeef4ad42a8bbb337@mail.gmail.com> In-Reply-To: <3bbf2fe10609120130l55c4590eha3628e7f1c21d8a7@mail.gmail.com> References: <200609100956.k8A9uD0P094639@repoman.freebsd.org> <20060911193600.7ab43fb6@Magellan.Leidinger.net> <courier.4505B01B.00012841@intron.ac> <200609111528.49054.jhb@freebsd.org> <20060912073021.pvw7p0mit4w4cs8s@webmail.leidinger.net> <3bbf2fe10609120130l55c4590eha3628e7f1c21d8a7@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
2006/9/12, Attilio Rao <attilio@freebsd.org>: > 2006/9/12, Alexander Leidinger <netchild@freebsd.org>: > > Quoting John Baldwin <jhb@freebsd.org> (from Mon, 11 Sep 2006 15:28:48 -0400): > > > > > I've only gotten this message when I've leaked memory in a zone. Do you have > > > an example self-contained kernel module that produces this? > > > > Download > > http://www.Leidinger.net/FreeBSD/linuxolator/linuxolator-p4.diff (or > > check out the p4-branch) and recompile the aio and linux modules. > > You might put the code under "Initialize the new context" > (linux_io_setup) into the init function for your UMA object, and so > the destructive pair. > > It might not solve your problem, but it is more elegant. BTW, the error that you receive effectively happens only on memory leak. This is called from the keg destructor (uma_core.c). Attilio -- Peace can only be achieved by understanding - A. Einstein
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3bbf2fe10609120147p343f48a4yeef4ad42a8bbb337>