From: Max Krasnyansky <maxk@qualcomm.com>
To: "Dave O" <cxreg@pobox.com>, linux-kernel@vger.kernel.org
Subject: Re: Oops from tun module
Date: Wed, 30 Jul 2003 14:25:49 -0700 [thread overview]
Message-ID: <5.1.0.14.2.20030730140614.01ce0a98@unixmail.qualcomm.com> (raw)
In-Reply-To: <34018.204.17.42.117.1059505497.squirrel@www.genericorp.net >
At 12:04 PM 7/29/2003, Dave O wrote:
>I added a tun/tap interface using tunctl(8) from the user-mode-linux
>project under 2.6.0-test1, which created a device tap0, owned by user 1000
>(tunctl -u 1000). In doing so, the tun module was automatically loaded,
>but showed a refcount of 0 in lsmod. I was able to successfully "rmmod
>tun", but after doing this every program that tried to open /proc/net/dev
>(including ifconfig) immediately segfaults and causes an Oops. I was able
>to modprobe tun.o back in and that restored sane behavior. I imagine the
>module should have had it's refcount incremented when the device is
>created.
TUN/TAP driver relies on the network core to do module reference counting.
It doesn't really do any cleanup in module_exit(). Module refcounting was
recently removed from the network core which apparently broke TUN/TAP
driver. btw 'misc' driver doesn't do any ref counting either.
I'll try to spend some time on it this week and fix both misc and TUN driver.
Max
next parent reply other threads:[~2003-07-30 21:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <34018.204.17.42.117.1059505497.squirrel@www.genericorp.net >
2003-07-30 21:25 ` Max Krasnyansky [this message]
2003-07-29 19:04 Dave O
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=5.1.0.14.2.20030730140614.01ce0a98@unixmail.qualcomm.com \
--to=maxk@qualcomm.com \
--cc=cxreg@pobox.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®