[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <1428571230.25985.243.camel@edumazet-glaptop2.roam.corp.google.com>
Date: Thu, 09 Apr 2015 02:20:30 -0700
From: Eric Dumazet <eric.dumazet@...il.com>
To: Tuan Bui <tuan.d.bui@...com>
Cc: netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
davem@...emloft.net, kuznet@....inr.ac.ru, jmorris@...ei.org,
kaber@...sh.net, yoshfuji@...ux-ipv6.org,
Jason Low <jason.low2@...com>,
Aswin Chandramouleeswaran <aswin@...com>,
Jun Li <jun.li@...com>, Haris Volos <haris.volos@...com>,
Wai Long <waiman.long@...com>,
hideaki.yoshifuji@...aclelinux.com, alan@...ux.intel.com,
gw4pts@...pts.ampr.org
Subject: Re: [BUG REPORT] kernel panic in tcp_sendpage() on null pointer
dereference
On Tue, 2015-04-07 at 17:01 -0700, Tuan Bui wrote:
> On Tue, 2015-04-07 at 16:33 -0700, Eric Dumazet wrote:
> > On Tue, 2015-04-07 at 15:57 -0700, Tuan Bui wrote:
> > > Hi all,
> > >
> > > I am consistently seeing this kernel panic on a 16 sockets machine
> > > running Spark PageRank workload using Docker. I am running RHEL 7.0
> > > stock kernel which is 3.10.0-123.el7.x86_64.
> >
> > Have you tried a recent upstream kernel ?
> >
>
> Yes I have tried an upstream v4.0-rc4 kernel. I was still getting the
> same kernel panic.
This looks like a use after free on one skb, but I see no smoking gun in
sendpage() paths.
You might try some debugging kernel build to detect this. (ASAN maybe)
--
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