From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dave Jones Subject: Re: ip6_dst_lookup_tail oops Date: Fri, 18 Jan 2013 10:20:23 -0500 Message-ID: <20130118152023.GA2116@redhat.com> References: <20130116145507.GA12244@redhat.com> <20130117152504.GC32586@redhat.com> <20130118124809.GA15977@hmsreliant.think-freely.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: netdev@vger.kernel.org To: Neil Horman Return-path: Received: from mx1.redhat.com ([209.132.183.28]:55097 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751544Ab3ARQQX (ORCPT ); Fri, 18 Jan 2013 11:16:23 -0500 Content-Disposition: inline In-Reply-To: <20130118124809.GA15977@hmsreliant.think-freely.org> Sender: netdev-owner@vger.kernel.org List-ID: On Fri, Jan 18, 2013 at 07:48:09AM -0500, Neil Horman wrote: > > Now I've hit it with rt->n = 2000000000000010. So I'm starting to > > think this is getting passed in directly from userspace somehow, as > > these values look like the output of my 'set a few random bits' routine > > that sometimes gets called for params. > > > > I'm having trouble mapping a corrupt sendmsg parameter to a messed up rt->n though. > > > Well, neighbor table entries for ipv6 get added over rtnetlink, ah, that's helpful. That explains why just fuzzing sendmsg alone won't hit this. > but it seems you > would have to be able to memory map the socket to get a pointer like that into > place. Trinity doesn't record the syscalls it makes does it? That might be > helpful in tracking this down. It does, but when it takes two days to hit something like this, you end up with gigabytes of data to look through. Dave