From: Dave Jones <davej@redhat.com>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org, kernel-team@fedoraproject.org
Subject: Re: NULL pointer dereference at __ip_route_output_key
Date: Mon, 2 Apr 2012 20:22:00 -0400 [thread overview]
Message-ID: <20120403002200.GA21262@redhat.com> (raw)
In-Reply-To: <20120402.200711.2234324385609269937.davem@davemloft.net>
On Mon, Apr 02, 2012 at 08:07:11PM -0400, David Miller wrote:
> > We just had this reported. Look familiar to anyone ?
>
> If you could unravel the source file and line the OOPS occurs at, I
> can look at these kinds of reports much faster. As it stands, when I
> see a Fedora OOPS, it's a long process for me:
Ok, I'll try and pull these apart for you in future, as I usually
have the bits for the most recent builds around.
> Anyways in this case dev_out is NULL when we read it around line
> 2798 of net/ipv4/route.c:
>
> dev_out = FIB_RES_DEV(res);
> fl4->flowi4_oif = dev_out->ifindex;
>
> and we are thus OOPS'ing on the dev_out->ifindex.
>
> Unfortunately I've never seen a report like this. If the reporter can
> reproduce, you can try to extract more information by doing something
> like this right after the dev_out assignment:
>
> if (!dev_out) {
> pr_crit("ipv4: FIB_RES_DEV() is NULL, nh_sel=%d\n",
> res.nh_sel);
> rth = ERR_PTR(-EINVAL);
> goto out;
> }
>
> This debugging will also avoid the NULL pointer crash at least for
> that particular invocation.
ok, I'll do a test build with this change for the user to try out.
Hopefully he can retrigger it.
thanks,
Dave
next prev parent reply other threads:[~2012-04-03 0:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-02 19:40 NULL pointer dereference at __ip_route_output_key Dave Jones
2012-04-03 0:07 ` David Miller
2012-04-03 0:22 ` Dave Jones [this message]
2012-04-03 0:34 ` David Miller
-- strict thread matches above, loose matches on Subject: below --
2012-04-19 14:58 Yevgen Pronenko
2012-05-10 20:49 ` David Miller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120403002200.GA21262@redhat.com \
--to=davej@redhat.com \
--cc=davem@davemloft.net \
--cc=kernel-team@fedoraproject.org \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.