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: <20100408175444.1e0da2c6@nehalam>
Date:	Thu, 8 Apr 2010 17:54:44 -0700
From:	Stephen Hemminger <shemminger@...tta.com>
To:	David Miller <davem@...emloft.net>
Cc:	emil.s.tantilov@...el.com, netdev@...r.kernel.org
Subject: Re: net-next: 2.6.34-rc1 regression: panic when running diagnostic
 on interface with IPv6

On Mon, 05 Apr 2010 16:53:17 -0700 (PDT)
David Miller <davem@...emloft.net> wrote:

> From: "Tantilov, Emil S" <emil.s.tantilov@...el.com>
> Date: Mon, 5 Apr 2010 17:50:38 -0600
> 
> > David Miller wrote:
> >> 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
> > 
> > Same in net-next:
> 
> Ok, Stephen please look into this, we've had this regression
> for almost two weeks now.

I can't reproduce it, on e1000e.
Since the symptoms match the original problem that you already fixed,
I have to assume that it is fixed but the reporter (Emil) had not
updated his kernel correctly.
--
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