From: Thierry Reding <thierry.reding@gmail.com>
To: David Ahern <dsa@cumulusnetworks.com>
Cc: Fabio Estevam <festevam@gmail.com>,
Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
Alexey Kuznetsov <kuznet@ms2.inr.ac.ru>,
James Morris <jmorris@namei.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
richard.alpe@ericsson.com
Subject: Re: [linux-next] oops in ip_route_input_noref
Date: Thu, 17 Sep 2015 10:58:52 +0200 [thread overview]
Message-ID: <20150917085850.GA7953@ulmo> (raw)
In-Reply-To: <55F984EF.4040503@cumulusnetworks.com>
[-- Attachment #1: Type: text/plain, Size: 1615 bytes --]
On Wed, Sep 16, 2015 at 09:04:15AM -0600, David Ahern wrote:
> On 9/16/15 9:00 AM, Fabio Estevam wrote:
> >On Wed, Sep 16, 2015 at 6:24 AM, Sergey Senozhatsky
> ><sergey.senozhatsky.work@gmail.com> wrote:
> >
> >>added by b7503e0cdb5dbec5d201aa69d8888c14679b5ae8
> >>
> >> net: Add FIB table id to rtable
> >>
> >> Add the FIB table id to rtable to make the information available for
> >> IPv4 as it is for IPv6.
> >
> >I see the same issue here when booting a mx25 ARM processor via NFS.
> >
> >defconfig is arch/arm/configs/imx_v4_v5_defconfig.
> >
>
> I am still not able to reproduce. While I work on a full Cumulus image for
> other test cases here's a patch to try; eagle eye Nikolay noted a potential
> use without init in the maze of goto's.
>
> Thanks,
> David
> diff --git a/net/ipv4/route.c b/net/ipv4/route.c
> index da427a4a33fe..80f7c5b7b832 100644
> --- a/net/ipv4/route.c
> +++ b/net/ipv4/route.c
> @@ -1712,6 +1712,7 @@ static int ip_route_input_slow(struct sk_buff *skb, __be32 daddr, __be32 saddr,
> goto martian_source;
>
> res.fi = NULL;
> + res.table = NULL;
> if (ipv4_is_lbcast(daddr) || (saddr == 0 && daddr == 0))
> goto brd_input;
>
> @@ -1834,6 +1835,7 @@ out: return err;
> RT_CACHE_STAT_INC(in_no_route);
> res.type = RTN_UNREACHABLE;
> res.fi = NULL;
> + res.table = NULL;
> goto local_input;
>
> /*
I was seeing the same oops as Fabio (except that the faulting address
was 0xb instead of 0x7) and after applying this patch I no longer see
it:
Tested-by: Thierry Reding <treding@nvidia.com>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-09-17 8:58 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-16 9:24 [linux-next] oops in ip_route_input_noref Sergey Senozhatsky
2015-09-16 11:50 ` Richard Alpe
2015-09-16 13:07 ` David Ahern
2015-09-16 13:53 ` Richard Alpe
2015-09-16 13:57 ` David Ahern
2015-09-16 14:08 ` Richard Alpe
2015-09-16 13:59 ` Richard Alpe
2015-09-16 14:00 ` David Ahern
2015-09-16 23:47 ` Sergey Senozhatsky
2015-09-17 7:26 ` Tomeu Vizoso
2015-09-16 13:24 ` David Ahern
2015-09-16 15:00 ` Fabio Estevam
2015-09-16 15:04 ` David Ahern
2015-09-17 8:58 ` Thierry Reding [this message]
2015-09-18 23:06 ` Andrew Morton
2015-09-19 14:34 ` David Ahern
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=20150917085850.GA7953@ulmo \
--to=thierry.reding@gmail.com \
--cc=davem@davemloft.net \
--cc=dsa@cumulusnetworks.com \
--cc=festevam@gmail.com \
--cc=jmorris@namei.org \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=richard.alpe@ericsson.com \
--cc=sergey.senozhatsky.work@gmail.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).