From: "Kevin P. Fleming" <kpfleming@cox.net>
To: LKML <linux-kernel@vger.kernel.org>
Subject: Re: [Bug 449] New: Kernel BUG when tun device is closed
Date: Fri, 07 Mar 2003 09:35:20 -0700 [thread overview]
Message-ID: <3E68CA48.2090905@cox.net> (raw)
In-Reply-To: <302800000.1047015141@[10.10.2.4]>
Martin J. Bligh wrote:
> http://bugme.osdl.org/show_bug.cgi?id=449
>
> Summary: Kernel BUG when tun device is closed (oops attached)
> Kernel Version: 2.5.64
> Status: NEW
> Severity: normal
> Owner: mochel@osdl.org
> Submitter: kpfleming@cox.net
>
>
> Distribution: heavily modified RedHat 7.3
> Hardware Environment: MSI K7T266-Pro2 motherboard, Athlon Thunderbird 1GHz CPU,
> (2) WD1600JB disks, etc.
> Software Environment: vtund-2.5
> Problem Description: vtund works fine normally (is in client mode on this
> system). when the server end of the link was shutdown, the client tried to close
> its open "tun" device. this action caused the oops below.
>
I have already updated this bug to show that Patrick's patch posted
yesterday appears to solve the problem.
prev parent reply other threads:[~2003-03-07 16:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-07 5:32 [Bug 449] New: Kernel BUG when tun device is closed Martin J. Bligh
2003-03-07 16:35 ` Kevin P. Fleming [this message]
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=3E68CA48.2090905@cox.net \
--to=kpfleming@cox.net \
--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.