All of lore.kernel.org
 help / color / mirror / Atom feed
From: "P. Christeas" <p_christ@hol.gr>
To: lkml <linux-kernel@vger.kernel.org>
Subject: lsmod ipv6 on -test9 shows many refs, lockd
Date: Tue, 4 Nov 2003 18:14:24 +0200	[thread overview]
Message-ID: <200311041814.24731.p_christ@hol.gr> (raw)

Question: is it normal for ipv6 module to have many refs while there is few 
ipv6 connections ?
My system is up for 3 days now. I have been using ACPI sleep and _ifconfig to 
alter the ip address_. 
lsmod gives:
	ipv6                  235904  34
and lsof -i6 only shows two ports listening on ipv6.
Even when I close all tcp (including v4) sockets, ipv6 still has around 10 
refs in lsmod.
Ten days ago (with -test7) I used to have a broken script for sshd that tried 
to bind to ipv6 every 20 mins. The result was that the count for ipv6.ko 
would reach as high as 900 w/o any bound sockets.
Does that constitute a leak? 

In other news, I haven't managed to trace the bug behind 'lockd', but I guess 
it's time I ask about it. After about 4 days uptime [1], both in -test7 and 
-test9, lockd BUGs at 'module.h, 296' . After that, nfs becomes unusable[2] 
and I have to reboot the kernel. The BUG is hit while I try to mount a nfs 
partition, which is being served by another 2.6 machine [3].
I can only report that this has happened. It may be related to the ipv6 leak, 
I guess..


[1] Every day, I switch from my home net to my work's net and back. I use 
ifconfig new_ip for that.
[2] lockd freezes, the 'mount' process gets <defunct> and nfs cannot be 
unloaded.
[3] At work, I mount nfs partitions to a *nix environment. I have not yet seen 
lockd freeze there.



             reply	other threads:[~2003-11-04 16:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-04 16:14 P. Christeas [this message]
2003-11-04 23:10 ` lsmod ipv6 on -test9 shows many refs, lockd David S. Miller

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200311041814.24731.p_christ@hol.gr \
    --to=p_christ@hol.gr \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.