| 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
| ||
|
Message-Id: <20130613.030129.858604303672324590.davem@davemloft.net> Date: Thu, 13 Jun 2013 03:01:29 -0700 (PDT) From: David Miller <davem@...emloft.net> To: eric.dumazet@...il.com Cc: rostedt@...dmis.org, sgunderson@...foot.com, linux-kernel@...r.kernel.org, netdev@...r.kernel.org, rusty@...tcorp.com.au Subject: Re: NULL pointer dereference when loading the gre module (3.10.0-rc4) From: Eric Dumazet <eric.dumazet@...il.com> Date: Thu, 06 Jun 2013 20:59:48 -0700 > On Thu, 2013-06-06 at 23:06 -0400, Steven Rostedt wrote: >> On Fri, Jun 07, 2013 at 12:16:56AM +0200, Steinar H. Gunderson wrote: >> > Hi, >> > >> > In 3.10.0-rc4, I get this on boot: >> > >> > [ 16.871043] BUG: unable to handle kernel NULL pointer dereference at 0000000000000003 >> > [ 16.879453] IP: [<ffffffffa0e52002>] 0xffffffffa0e52001 >> >> Strange, kallsyms should have registered the address already, even if it >> crashed on early module load. Not sure why it's not reporting it. Well, >> it seems to have reported some of the symbols of ip_gre below. Maybe >> this pointer is just totally screwed up. > > I could not reproduce this here. > > Steinar, please make sure you recompiled your modules, because this > looks like you loaded old modules. I applied Eric's fixed version of the patch, thanks. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists