On Tue, Mar 06, 2007 at 02:08:43PM +0100, Steinar H. Gunderson wrote:
> Package: libblkid1
> Version: 1.39+1.40-WIP-2006.11.14+dfsg-1
> Severity: grave
> Tags: patch
>
> (RMs: I'm unsure if this should be fixed for etch or not, given that I
> do not know of anything in etch that actually uses this library enough
> for it to leak. Feel free to downgrade or tag etch-ignore, of course.)
>
> nfs-kernel-server 1.0.12 has started using libblkid, and leaks absurd
> amounts of memory (in the order of several megabytes per minute).
> Tracing using Omega (which is not yet in Debian, but nevertheless really
> useful) tracked the leaks down to libblkid. I've attached a diff that
> fixes the issues for me, and allows me to run nfs-kernel-server with
> only minor leaks (which I'll take with nfs-utils upstream, as they are
> not libblkid1 related).
Yikes, what blkid function is rpc.mountd calling all the time which is
causing this kind of memory leakage? Sounds like a bad thing from a
power/CPU utilization standpoint (note to self; shut down rpc.mountd
when I'm running on batteries on my laptop). I'm also curious why we
only discovered the problem this late in the freeze....
Oh, I see, because nfs-kernel-server 1.0.10 is in testing, and 1.0.12
is in unstable. I assume it's unlikely that nfs-kernel-server 1.0.12
is going to migrate to testing?
OK, release managers, the memory leak primarily occurs in the device
mapper probing code, and an additional leak when there is a partition
which does not have a valid filesystem known to blkid. rpc.mountd is,
as far as I know, the first long-lived daemon using blkid, and it's
apparently using it in a somewhat "interesting" way which is the
system to constantly reprobe the disk information (if it is leaking
megabytes per minute). The patch looks reasonably sane and low risk
based on a on-paper examination of the code changes --- but if
nfs-kernel-server 1.0.12 isn't going into etch, I'd say it's
borderline whether or not we include this patch into the e2fsprogs
upload I was about to do.
What say ye?
- Ted
P.S. I really want to look at the sources of nfs-kernel-server 1.0.12
and see what it's *doing* that could be provoking a memory leak of the
rate that you are describing. The memory leak is clearly blkid's
fault, but the rate at which memory is leaking smells very fishy.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
