netdev - Re: BUG: unable to handle kernel paging request at 00000000d8be176d

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

Message-ID: <1341555227.3265.54.camel@edumazet-glaptop>
Date:	Fri, 06 Jul 2012 08:13:47 +0200
From:	Eric Dumazet <eric.dumazet@...il.com>
To:	Fengguang Wu <wfg@...ux.intel.com>
Cc:	David Miller <davem@...emloft.net>, netdev@...r.kernel.org,
	Steffen Klassert <steffen.klassert@...unet.com>
Subject: Re: BUG: unable to handle kernel paging request at 00000000d8be176d

On Fri, 2012-07-06 at 13:58 +0800, Fengguang Wu wrote:
> On Thu, Jul 05, 2012 at 02:22:00PM -0700, David Miller wrote:
> > 
> > Steffen Klassert posted a patch which fixes this.
> 
> Steffen's patch converts one oops message into another.
> 
> tree:   git://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git master
> head:   700db99d0140e9da2a31e08ebd3e1b121691aa26
> commit: a2de86f63cfc92f7aaf11e7b9d9f2150946a1622 [1/2] ipv6: Initialize the neighbour pointer of rt6_info on allocation
> 
> x86_64-allyesdebian         BBB

Please try :

diff --git a/net/ipv6/ip6_output.c b/net/ipv6/ip6_output.c
index 6d9c0ab..c6af596 100644
--- a/net/ipv6/ip6_output.c
+++ b/net/ipv6/ip6_output.c
@@ -975,7 +975,7 @@ static int ip6_dst_lookup_tail(struct sock *sk,
 	 * dst entry of the nexthop router
 	 */
 	rcu_read_lock();
-	rt = (struct rt6_info *) dst;
+	rt = (struct rt6_info *) *dst;
 	n = rt->n;
 	if (n && !(n->nud_state & NUD_VALID)) {
 		struct inet6_ifaddr *ifp;


--
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