From: Markus Trippelsdorf <markus@trippelsdorf.de>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: Tomasz Mloduchowski <q@qdot.me>, netdev@vger.kernel.org
Subject: Re: TCP out of memory - possible bug [3.18.0-rc3] / sched?
Date: Sun, 4 Jan 2015 22:39:43 +0100 [thread overview]
Message-ID: <20150104213943.GB1710@x4> (raw)
In-Reply-To: <1420405287.32621.8.camel@edumazet-glaptop2.roam.corp.google.com>
On 2015.01.04 at 13:01 -0800, Eric Dumazet wrote:
> On Sun, 2015-01-04 at 09:42 +0100, Markus Trippelsdorf wrote:
>
> > Any news on this issue?
> >
> > I stumbled across the same problem today with 3.19.0-rc2:
>
> What make you think it was fixed in 3.19.0-rc2 ?
Nothing.
> Have you tried a bisection ?
It was a one time event for me. So a bisection is out of the question.
But Tomasz wrote that he can reproduce the issue reliably.
Have you tried a bisection, Tomasz?
--
Markus
prev parent reply other threads:[~2015-01-04 21:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-03 18:59 TCP out of memory - possible bug [3.18.0-rc3] / sched? Tomasz Mloduchowski
2014-11-03 19:41 ` Eric Dumazet
2015-01-04 8:42 ` Markus Trippelsdorf
2015-01-04 21:01 ` Eric Dumazet
2015-01-04 21:39 ` Markus Trippelsdorf [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=20150104213943.GB1710@x4 \
--to=markus@trippelsdorf.de \
--cc=eric.dumazet@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=q@qdot.me \
/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