From: Subash Abhinov Kasiviswanathan <subashab@codeaurora.org>
To: Neal Cardwell <ncardwell@google.com>
Cc: Netdev <netdev@vger.kernel.org>,
Yuchung Cheng <ycheng@google.com>,
Eric Dumazet <eric.dumazet@gmail.com>
Subject: Re: Crash when receiving FIN-ACK in TCP_FIN_WAIT1 state
Date: Mon, 21 Oct 2019 18:04:43 -0600 [thread overview]
Message-ID: <f9ae970c12616f61c6152ebe34019e2b@codeaurora.org> (raw)
In-Reply-To: <CADVnQykjfjPNv6F1EtWWvBT0dZFgf1QPDdhNaCX3j3bFCkViwA@mail.gmail.com>
> Interesting! As tcp_input.c summarizes, "packets_out is
> SND.NXT-SND.UNA counted in packets". In the normal operation of a
> socket, tp->packets_out should not be 0 if any of those other fields
> are non-zero.
>
> The tcp_write_queue_purge() function sets packets_out to 0:
>
>
> https://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git/tree/net/ipv4/tcp.c?h=v4.19#n2526
>
> So the execution of tcp_write_queue_purge() before this point is one
> way for the socket to end up in this weird state.
>
In one of the instances, the values are tp->snd_nxt = 1016118098,
tp->snd_una = 1016047820
tp->mss_cache = 1378
I assume the number of outstanding segments should be
(tp->snd_nxt - tp->snd_una)/tp->mss_cache = 51
tp->packets_out = 0 and tp->sacked_out = 158 in this case.
>> > Yes, one guess would be that somehow the skbs in the retransmit queue
>> > have been freed, but tp->sacked_out is still non-zero and
>> > tp->highest_sack is still a dangling pointer into one of those freed
>> > skbs. The tcp_write_queue_purge() function is one function that fees
>> > the skbs in the retransmit queue and leaves tp->sacked_out as non-zero
>> > and tp->highest_sack as a dangling pointer to a freed skb, AFAICT, so
>> > that's why I'm wondering about that function. I can't think of a
>> > specific sequence of events that would involve tcp_write_queue_purge()
>> > and then a socket that's still in FIN-WAIT1. Maybe I'm not being
>> > creative enough, or maybe that guess is on the wrong track. Would you
>> > be able to set a new bit in the tcp_sock in tcp_write_queue_purge()
>> > and log it in your instrumentation point, to see if
>> > tcp_write_queue_purge() was called for these connections that cause
>> > this crash?
I've queued up a build which logs calls to tcp_write_queue_purge and
clears tp->highest_sack and tp->sacked_out. I will let you know how
it fares by end of week.
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2019-10-22 0:05 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-20 20:25 Crash when receiving FIN-ACK in TCP_FIN_WAIT1 state Subash Abhinov Kasiviswanathan
2019-10-20 22:16 ` Neal Cardwell
2019-10-20 23:15 ` Subash Abhinov Kasiviswanathan
2019-10-21 1:20 ` Neal Cardwell
2019-10-21 2:45 ` Subash Abhinov Kasiviswanathan
2019-10-21 11:47 ` Neal Cardwell
2019-10-22 0:04 ` Subash Abhinov Kasiviswanathan [this message]
2019-10-22 1:28 ` Neal Cardwell
2019-10-29 1:36 ` Subash Abhinov Kasiviswanathan
2019-10-30 17:13 ` Neal Cardwell
2019-10-30 18:27 ` Subash Abhinov Kasiviswanathan
2019-10-30 21:48 ` Josh Hunt
2019-10-31 1:27 ` Eric Dumazet
2019-11-27 5:30 ` Eric Dumazet
2019-11-30 2:51 ` subashab
2019-11-30 5:39 ` Avinash Patil
2019-12-02 2:23 ` Eric Dumazet
[not found] ` <0101016eba38455f-e79cd85a-a807-4309-bf3b-8a788135f3f2-000000@us-west-2.amazonses.com>
2019-12-03 17:24 ` Josh Hunt
2019-10-31 0:38 ` Eric Dumazet
2019-10-31 1:17 ` Subash Abhinov Kasiviswanathan
2019-10-21 14:17 ` Eric Dumazet
2019-10-21 17:40 ` Subash Abhinov Kasiviswanathan
2019-10-21 18:10 ` Josh Hunt
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=f9ae970c12616f61c6152ebe34019e2b@codeaurora.org \
--to=subashab@codeaurora.org \
--cc=eric.dumazet@gmail.com \
--cc=ncardwell@google.com \
--cc=netdev@vger.kernel.org \
--cc=ycheng@google.com \
/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).