From: Eric Dumazet <eric.dumazet@gmail.com>
To: dormando <dormando@rydia.net>
Cc: David Miller <davem@davemloft.net>, netdev <netdev@vger.kernel.org>
Subject: Re: [PATCH] tcp: dont handle MTU reduction on LISTEN socket
Date: Tue, 19 Mar 2013 21:51:15 -0700 [thread overview]
Message-ID: <1363755075.3333.2.camel@edumazet-glaptop> (raw)
In-Reply-To: <alpine.DEB.2.02.1303192114580.4793@dflat>
On Tue, 2013-03-19 at 21:16 -0700, dormando wrote:
> Thanks! We are all incredibly appreciative of your quick help with this.
>
Well, given that I introduced the bug, I better fix it ;)
> I have 3.8.3 + this patch running on our machine for 20 hours so far. We
> haven't had a kernel newer than 3.2 go for a full day before. I'm giving
> it another peak cycle before calling it dead but it looks like you nailed
> it.
>
> I assume you no longer need the kernel disassembly?
Cross our fingers that the bug was really this one.
If you have another crash, please let us know.
Thanks !
prev parent reply other threads:[~2013-03-20 4:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-18 17:01 [PATCH] tcp: dont handle MTU reduction on LISTEN socket Eric Dumazet
2013-03-18 17:32 ` David Miller
2013-03-20 4:16 ` dormando
2013-03-20 4:51 ` 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=1363755075.3333.2.camel@edumazet-glaptop \
--to=eric.dumazet@gmail.com \
--cc=davem@davemloft.net \
--cc=dormando@rydia.net \
--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