lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20090415152946.90bbdfc0.akpm@linux-foundation.org>
Date:	Wed, 15 Apr 2009 15:29:46 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	netdev@...r.kernel.org, maxk@...lcomm.com, vtun@...ice.satix.net,
	Ayaz Abdulla <aabdulla@...dia.com>
Cc:	bugzilla-daemon@...zilla.kernel.org
Subject: Re: [Bugme-new] [Bug 13097] New: Kernel will freeze network after
 using a tun/tap device


(switched to email.  Please respond via emailed reply-to-all, not via the
bugzilla web interface).

Big fat regression!

On Wed, 15 Apr 2009 22:19:06 GMT
bugzilla-daemon@...zilla.kernel.org wrote:

> http://bugzilla.kernel.org/show_bug.cgi?id=13097
> 
>            Summary: Kernel will freeze network after using a tun/tap
>                     device
>            Product: Drivers
>            Version: 2.5
>     Kernel Version: 2.6.30-rc2
>           Platform: All
>         OS/Version: Linux
>               Tree: Mainline
>             Status: NEW
>           Severity: normal
>           Priority: P1
>          Component: Network
>         AssignedTo: drivers_network@...nel-bugs.osdl.org
>         ReportedBy: fragabr@...il.com
>         Regression: Yes
> 
> 
> I choose the forcedeth driver to report this bug because I think it's related
> to forcedeth and not tun/tap driver, although I can be wrong.
> 
> With 2.6.29 kernel everything works fine, but with 2.6.30-rc2, a simple ping to
> a tun/tap device (for example ping to a vpn using openvpn) will freeze the
> network. In X I can't even use the keyboard anymore.
> 
> It just happens with a tun/tap device, not with a normal ethernet device or a
> normal internet connection.
> 
> If you think it's a tun/tap driver problem, please change the bug, but as I'm
> not completely sure, I choose forcedeth.

An obvious question would be: are you able to test the same setup with
a different type of network card?

--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ