From: Eric Dumazet <eric.dumazet@gmail.com>
To: "Lothar Waßmann" <LW@KARO-electronics.de>
Cc: netdev@vger.kernel.org, "David S. Miller" <davem@davemloft.net>,
David Ahern <dsa@cumulusnetworks.com>
Subject: Re: [linux-next] Regression in net/ipv4/route.c
Date: Fri, 18 Sep 2015 03:57:19 -0700 [thread overview]
Message-ID: <1442573839.7946.16.camel@edumazet-glaptop2.roam.corp.google.com> (raw)
In-Reply-To: <20150918101123.77d48b84@ipc1.ka-ro>
On Fri, 2015-09-18 at 10:11 +0200, Lothar Waßmann wrote:
>
> I bisected it down to: commit b7503e0cdb5d (net: Add FIB table id to rtable)
>
> There may be other ways to produce the same crash too, but I did not
> test any further.
>
>
> Lothar Waßmann
Fixed with
http://git.kernel.org/cgit/linux/kernel/git/davem/net-next.git/commit/?id=bde6f9ded1bd37ff27a042dcb968e104d92b02c1
Thanks Lothar
prev parent reply other threads:[~2015-09-18 10:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-18 8:11 [linux-next] Regression in net/ipv4/route.c Lothar Waßmann
2015-09-18 10:57 ` Eric Dumazet [this message]
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=1442573839.7946.16.camel@edumazet-glaptop2.roam.corp.google.com \
--to=eric.dumazet@gmail.com \
--cc=LW@KARO-electronics.de \
--cc=davem@davemloft.net \
--cc=dsa@cumulusnetworks.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox