From: Fernando Soto <fernando.soto@gmail.com>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: netdev@vger.kernel.org
Subject: Re: WARNING: at net/core/dst.c:274 dst_release+0x2d/0x56()
Date: Thu, 18 Jul 2013 11:55:28 -0400 [thread overview]
Message-ID: <CADCFf2gS3sS0hL1pr-P+LUVqhvBEMLy-Q8hRp-R8c06e4qtp2g@mail.gmail.com> (raw)
In-Reply-To: <1374083689.6097.19.camel@edumazet-glaptop>
Hi Eric,
I applied the patch to the latest 3.10.1 and the network is working
fine. I'm not sure if it is due to the patch or any other changes
between 3.10.0 and 3.10.1.
I'll leave iperf running for a few days. Looks good so far.
Thank you!
Fernando
On Wed, Jul 17, 2013 at 1:54 PM, Eric Dumazet <eric.dumazet@gmail.com> wrote:
> On Wed, 2013-07-17 at 09:19 -0400, Fernando Soto wrote:
>> Hi Eric,
>>
>> Just to let you know that I have performed same tests with 3.4.52 and
>> it works fine.
>> Kernel 3.10 had another issue that prevented me from running the same
>> tests: network dies as soon as I launch iperf - no kernel errors, but
>> it simply doesn't work.
>> I'll stick to 3.4.52. Thanks for your help.
>
> This might be relevant : http://patchwork.ozlabs.org/patch/259596/
>
>
next prev parent reply other threads:[~2013-07-18 15:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-02 21:05 WARNING: at net/core/dst.c:274 dst_release+0x2d/0x56() Fernando Soto
2013-07-02 21:13 ` Eric Dumazet
2013-07-02 21:44 ` Fernando Soto
2013-07-04 12:21 ` Fernando Soto
2013-07-04 15:08 ` Eric Dumazet
2013-07-04 15:56 ` Fernando Soto
2013-07-17 13:19 ` Fernando Soto
2013-07-17 17:54 ` Eric Dumazet
2013-07-18 15:55 ` Fernando Soto [this message]
2013-07-18 16:37 ` Eric Dumazet
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=CADCFf2gS3sS0hL1pr-P+LUVqhvBEMLy-Q8hRp-R8c06e4qtp2g@mail.gmail.com \
--to=fernando.soto@gmail.com \
--cc=eric.dumazet@gmail.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;
as well as URLs for NNTP newsgroup(s).