From: Willy Tarreau <w@1wt.eu>
To: Frans Klaver <fransklaver@gmail.com>
Cc: starlight.2015q2@binnacle.cx,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
netdev <netdev@vger.kernel.org>
Subject: Re: 2.6.32.66 tcp regression OOPs
Date: Mon, 1 Jun 2015 09:49:22 +0200 [thread overview]
Message-ID: <20150601074922.GA28740@1wt.eu> (raw)
In-Reply-To: <CAH6sp9O9sqKuamwF38JZLh+K2QKXNB7RRJ8cPtz+1h6MV7foYg@mail.gmail.com>
Hi,
On Mon, Jun 01, 2015 at 09:00:21AM +0200, Frans Klaver wrote:
> [cc: Willy Tarreau]
>
> On Mon, Jun 1, 2015 at 3:26 AM, <starlight.2015q2@binnacle.cx> wrote:
> > Hello,
> >
> > Apoligies if I have submitted to the wrong lists.
> >
> > Encountered a regression in
> > 2.6.32.66 relative to 2.6.32.65.
> >
> > Crash eight minutes after boot.
> >
> > Will responded with additional details
> > if the OOPS is not sufficent.
> >
> > Best Regards
> >
>
> Did you bisect it?
Eric Dumazet notified me that of something possibly similar due to
a mistake I made when backporting a fix by hand.
Please apply the following patch to see if it fixes the problem :
diff --git a/net/ipv4/tcp_output.c b/net/ipv4/tcp_output.c
index 5339f066234b..d1e2895bb63c 100644
--- a/net/ipv4/tcp_output.c
+++ b/net/ipv4/tcp_output.c
@@ -2136,7 +2136,7 @@ void tcp_send_fin(struct sock *sk)
*/
if (tskb && (tcp_send_head(sk) || tcp_memory_pressure)) {
coalesce:
- TCP_SKB_CB(skb)->flags |= TCPCB_FLAG_FIN;
+ TCP_SKB_CB(tskb)->flags |= TCPCB_FLAG_FIN;
TCP_SKB_CB(tskb)->end_seq++;
tp->write_seq++;
if (!tcp_send_head(sk)) {
Thanks,
Willy
next prev parent reply other threads:[~2015-06-01 7:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-01 1:26 2.6.32.66 tcp regression OOPs starlight.2015q2
2015-06-01 7:00 ` Frans Klaver
2015-06-01 7:49 ` Willy Tarreau [this message]
2015-06-01 15:32 ` starlight.2015q2
2015-06-01 15:47 ` Willy Tarreau
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=20150601074922.GA28740@1wt.eu \
--to=w@1wt.eu \
--cc=fransklaver@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=starlight.2015q2@binnacle.cx \
/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).