netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Avinash Patil <avinashapatil@gmail.com>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: netdev@vger.kernel.org
Subject: Re: Possible bug in TCP retry logic/Kernel crash
Date: Fri, 15 Nov 2019 17:52:27 -0800	[thread overview]
Message-ID: <CAJwzM1=uv8NG=upCiRonvA504dn1u5Tj5DNM83BCSMbSmwvLuw@mail.gmail.com> (raw)
In-Reply-To: <0d553faa-b665-14cf-e977-d2b0ff3d763e@gmail.com>

Hi Eric,

I integrated all patches till 4.19.83 as per your suggestion.
Unfortunately, I still see crash.

[  991.291968] [ECR   ]: 0x00230400 => Misaligned r/w from 0x00000001
[  991.299766] [EFA   ]: 0x00000001
[  991.299766] [BLINK ]: tcp_clean_rtx_queue+0x2a4/0xc88
[  991.299766] [ERET  ]: __list_del_entry_valid+0x12/0x1a0
[  991.313350] [STAT32]: 0x00000206 : K         E2 E1
[  991.318323] BTA: 0x8b188843   SP: 0x8f04fcf4  FP: 0x00000000
[  991.323977] LPS: 0x8b2e2942  LPE: 0x8b2e2946 LPC: 0x00000000
[  991.329660] r00: 0x8cbf2224  r01: 0x8cbf21c0 r02: 0x6e6c53fe
[  991.329660] r03: 0x00000001  r04: 0x00000000 r05: 0x39ef6f1d
[  991.329660] r06: 0x8f3e3180  r07: 0x00000000 r08: 0x3b14d54c
[  991.329660] r09: 0x00000000  r10: 0x0000c0ef r11: 0x00000000
[  991.329660] r12: 0x04c80000  r13: 0x8cbf21c0 r14: 0x00000000
[  991.329660] r15: 0x00000000  r16: 0x00000001 r17: 0x00000000
[  991.329660] r18: 0x8f3e3580  r19: 0x8f3e2d80 r20: 0x00000004
[  991.329660] r21: 0x8f04fd7c  r22: 0x00000001 r23: 0x3b14d54c
[  991.329660] r24: 0x00000000  r25: 0x8f0315c0
[  991.329660]
[  991.329660]
[  991.382333]
[  991.382333] Stack Trace:
[  991.386374] Firmware build version: avinashp6_bbic5_a-cl103643
[  991.386374] Firmware configuration: pearl_10gax_config
[  991.386374] Hardware ID           : 65535
[  991.401461]   __list_del_entry_valid+0x12/0x1a0
[  991.406125]   tcp_clean_rtx_queue+0x2a4/0xc88
[  991.410618]   tcp_ack+0x484/0x914
[  991.414073]   tcp_rcv_established+0x538/0x724
[  991.418564]   tcp_v4_do_rcv+0xda/0x120
[  991.422456]   tcp_v4_rcv+0x954/0xa7c
[  991.426105]   ip_local_deliver+0x72/0x208
[  991.430257]   process_backlog+0xbe/0x1b0
[  991.434319]   net_rx_action+0x106/0x294
[  991.438286]   __do_softirq+0xf0/0x218
[  991.442014]   run_ksoftirqd+0x2a/0x3c
[  991.445812]   smpboot_thread_fn+0xb4/0x10c
[  991.450054]   kthread+0xd8/0xdc
[  991.453338]   ret_from_fork+0x18/0x1c
[  991.457067]

Thank you!

-Avinash

On Sun, Nov 10, 2019 at 3:48 PM Eric Dumazet <eric.dumazet@gmail.com> wrote:
>
>
>
> 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()
>

  parent reply	other threads:[~2019-11-16  1:52 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
2019-11-11  2:20   ` Avinash Patil
2019-11-16  1:52   ` Avinash Patil [this message]
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='CAJwzM1=uv8NG=upCiRonvA504dn1u5Tj5DNM83BCSMbSmwvLuw@mail.gmail.com' \
    --to=avinashapatil@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).