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: <637AD4DF2E595346BAB0DF8C46F3A2B0032921A7@BGSMSX101.gar.corp.intel.com>
Date:	Tue, 23 Sep 2014 11:11:53 +0000
From:	"Sharma, Karun" <karun.sharma@...el.com>
To:	Eric Dumazet <eric.dumazet@...il.com>
CC:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: RE: 3.17 kernel crash while loading IPoIB

Thanks Eric. Yes, the commits below have fixed the issue.

Regards,
Karun Sharma


-----Original Message-----
From: Eric Dumazet [mailto:eric.dumazet@...il.com] 
Sent: Tuesday, September 23, 2014 2:36 PM
To: Sharma, Karun
Cc: linux-kernel@...r.kernel.org; netdev@...r.kernel.org
Subject: Re: 3.17 kernel crash while loading IPoIB

On Tue, 2014-09-23 at 05:15 +0000, Sharma, Karun wrote:
> Hello:
> 
> I am facing an issue wherein kernel 3.17 crashes while loading IPoIB 
> module. I guess the issue discussed in this thread
> (https://www.mail-archive.com/linux-rdma@vger.kernel.org/msg20963.html) is similar.
> 
> We were able to reproduce the issue with RC6 also. Here are the steps 
> I followed:
> 
> I compiled and installed 3.17 kernel on top of RHEL 6.5. 
> Then I changed rdma.conf to not load IPoIB (If I don't do this, the 
> kernel crashes while booting and starting RDMA service.) After the 
> server comes up, I just did "modprobe ib_ipoib" and kernel crashes.
> Please see below the kernel back trace.
> 
> Seeing the announcement, it looks like RC6 will be the last RC for
> 3.17 kernel. Will the release happen with this issue? Is there any 
> workaround available for this issue?
> I am not sure what mechanism/process is used to report issue to kernel 
> community.
> 
> Regards
> Karun

This seems fixed now :

http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=257117862634d89de33fec74858b1a0ba5ab444b

http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=b49fe36208b45f76dfbcfcd3afd952a33fa9f5ce


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ