netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eric Dumazet <eric.dumazet@gmail.com>
To: Avinash Patil <avinashapatil@gmail.com>, netdev@vger.kernel.org
Subject: Re: Possible bug in TCP retry logic/Kernel crash
Date: Sun, 10 Nov 2019 15:47:59 -0800	[thread overview]
Message-ID: <0d553faa-b665-14cf-e977-d2b0ff3d763e@gmail.com> (raw)
In-Reply-To: <CAJwzM1k7iW9tJZiO-JhVbnT-EmwaJbsroaVbJLnSVY-tyCzjLQ@mail.gmail.com>



On 11/9/19 9:59 PM, Avinash Patil wrote:
> Hi everyone,
> 
> Kernel: Linux 4.19.35 kernel built from linux-stable
> 

This is quite an old version.

Please upgrade to the latest one.

$ git log --oneline v4.19.35..v4.19.82 -- net/ipv4/tcp*c
3fdcf6a88ded2bb5c3c0f0aabaff253dd3564013 tcp: better handle TCP_USER_TIMEOUT in SYN_SENT state
67fe3b94a833779caf4504ececa7097fba9b2627 tcp: fix tcp_ecn_withdraw_cwr() to clear TCP_ECN_QUEUE_CWR
5977bc19ce7f1ed25bf20d09d8e93e56873a9abb tcp: remove empty skb from write queue in error cases
6f3126379879bb2b9148174f0a4b6b65e04dede9 tcp: inherit timestamp on mtu probe
1b200acde418f4d6d87279d3f6f976ebf188f272 tcp: Reset bytes_acked and bytes_received when disconnecting
c60f57dfe995172c2f01e59266e3ffa3419c6cd9 tcp: fix tcp_set_congestion_control() use from bpf hook
6323c238bb4374d1477348cfbd5854f2bebe9a21 tcp: be more careful in tcp_fragment()
dad3a9314ac95dedc007bc7dacacb396ea10e376 tcp: refine memory limit test in tcp_fragment()
59222807fcc99951dc769cd50e132e319d73d699 tcp: enforce tcp_min_snd_mss in tcp_mtu_probing()
7f9f8a37e563c67b24ccd57da1d541a95538e8d9 tcp: add tcp_min_snd_mss sysctl
ec83921899a571ad70d582934ee9e3e07f478848 tcp: tcp_fragment() should apply sane memory limits
c09be31461ed140976c60a87364415454a2c3d42 tcp: limit payload size of sacked skbs
6728c6174a47b8a04ceec89aca9e1195dee7ff6b tcp: tcp_grow_window() needs to respect tcp_space()


  reply	other threads:[~2019-11-10 23:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-10  5:59 Possible bug in TCP retry logic/Kernel crash Avinash Patil
2019-11-10 23:47 ` Eric Dumazet [this message]
2019-11-11  2:20   ` Avinash Patil
2019-11-16  1:52   ` Avinash Patil
2019-11-16  2:01     ` Eric Dumazet
2019-11-16  2:07       ` Avinash Patil
2019-11-16  2:29         ` Eric Dumazet
2019-11-19 22:39           ` Avinash Patil

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=0d553faa-b665-14cf-e977-d2b0ff3d763e@gmail.com \
    --to=eric.dumazet@gmail.com \
    --cc=avinashapatil@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).