netdev - Re: net-next: 2.6.34-rc1 regression: panic when running diagnostic on interface with IPv6

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20100405.161221.159637463.davem@davemloft.net>
Date:	Mon, 05 Apr 2010 16:12:21 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	emil.s.tantilov@...el.com
Cc:	shemminger@...tta.com, netdev@...r.kernel.org
Subject: Re: net-next: 2.6.34-rc1 regression: panic when running diagnostic
 on interface with IPv6 

From: "Tantilov, Emil S" <emil.s.tantilov@...el.com>
Date: Mon, 5 Apr 2010 17:03:56 -0600

> David Miller wrote:
>> From: "Tantilov, Emil S" <emil.s.tantilov@...el.com>
>> Date: Tue, 23 Mar 2010 12:28:08 -0600
>> 
>>> Bisecting points to this patch:
>>> http://git.kernel.org/?p=linux/kernel/git/davem/net-next-2.6.git;a=commitdiff;h=84e8b803f1e16f3a2b8b80f80a63fa2f2f8a9be6
>>> 
>>> And I confirmed that the issue goes away after reverting it.
>>> 
>>> Steps to reproduce:
>>> 1. Load the driver and configure IPv6 address.
>>> 2. Run ethtool diag:
>>> ethtool -t eth0
>>> 
>>> 3. If this doesn't brake it try again, or just do ifdown/up. Other
>>> operations on the interface will eventually panic the system: 
>> 
>> Stephen please fix this, thanks.
> 
> Just FYI - I still see this issue with latest pull from net-2.6.

It's net-next-2.6 that introduced the problem and has the follow-on
fixes, not net-2.6
--
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