netdev - RE: PROBLEM: [3.4] neigh_destroy() crashes on unplug netdev.

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-prev] [day] [month] [year] [list]

Message-ID: <E694983F62A0954788A62E997021A9C3109443@JPEX011.apo.epson.net>
Date:	Thu, 15 Jan 2015 07:50:41 +0000
From:	Nakashima Akihiro <Nakashima.Akihiro@....epson.co.jp>
To:	Eric Dumazet <eric.dumazet@...il.com>
CC:	"davem@...emloft.net" <davem@...emloft.net>,
	"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
	Ueda Motoki <Ueda.Motoki@....epson.co.jp>,
	"Otsu Takahiro" <Otsu.Takahiro@....epson.co.jp>,
	Tomono Mitsunori <Tomono.Mitsunori@....epson.co.jp>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: PROBLEM: [3.4] neigh_destroy() crashes on unplug netdev.

Dear Eric:

3.6 or later kernels (including recent mainline) do not have this problem.
3.4.105 is based on an old kernel, but it is a latest kernel of 3.4 LTS branch.
I think it is better to backport 20 patches to LTS branch.
But if you do not have such support policy, I will apply these patches to my 3.4 kernel only.

Thanks

-----Original Message-----
From: Eric Dumazet [mailto:eric.dumazet@...il.com] 
Sent: Thursday, January 15, 2015 4:03 PM
To: Nakashima Akihiro
Cc: davem@...emloft.net; netdev@...r.kernel.org; Ueda Motoki; Otsu Takahiro; Tomono Mitsunori; linux-kernel@...r.kernel.org
Subject: Re: PROBLEM: [3.4] neigh_destroy() crashes on unplug netdev.

On Thu, 2015-01-15 at 05:57 +0000, Nakashima Akihiro wrote:
> Dear David and networking developers:
> 
> I got kernel panic on 3.4.105 kernel.
> Please see a report below.

Please try a recent kernel.

We are not going to debug such an old one, given there are chances we already fixed the problem ages ago.

Thanks