From: Stephen Hemminger <stephen@networkplumber.org>
To: netdev@vger.kernel.org
Subject: Fw: [Bug 219221] New: TCP connection/socket gets stuck and the handshaking is delayed
Date: Mon, 2 Sep 2024 08:43:35 -0700 [thread overview]
Message-ID: <20240902084335.1e048358@hermes.local> (raw)
Begin forwarded message:
Date: Mon, 02 Sep 2024 14:25:13 +0000
From: bugzilla-daemon@kernel.org
To: stephen@networkplumber.org
Subject: [Bug 219221] New: TCP connection/socket gets stuck and the handshaking is delayed
https://bugzilla.kernel.org/show_bug.cgi?id=219221
Bug ID: 219221
Summary: TCP connection/socket gets stuck and the handshaking
is delayed
Product: Networking
Version: 2.5
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P3
Component: IPV4
Assignee: stephen@networkplumber.org
Reporter: zbal1977@gmail.com
Regression: No
Created attachment 306806
--> https://bugzilla.kernel.org/attachment.cgi?id=306806&action=edit
working TCP connection PCAP file
Hi,
We have a client/server application which is developed a long time ago. It has
been running in production for more than 10 years. The client is a Windows
application written in C++, and the server-side component is written in Java8.
This client/server software has been working fine for a long time on Linux
servers. Currently, we use AlmaLinux 9. It was working on AlmaLinux 9 until
updating the kernel.
So, when we update the Linux kernel from "5.14.0-362.13.1.el9_3.x86_64" to
"kernel-5.14.0-427.31.1.el9_4.x86_64" the application gets unstable: The client
drops the connection based due to not receiving messages in the proper time. We
notice delays, the client just waiting for the response from the server. The
issue is always reproducible with the new kernel. And if we go back to the old
kernel, the problem is gone. We kept running the test for hours in both cases.
I attach the PCAP file created on the working system running with the old
kernel (5.14.0-362). Additionally, I attach another PCAP file created on the
non-working system. The difference is the kernel (5.14.0-427). All other
components are the same.
Please analyze it and let us know how to fix it. Whether it is a general issue
in the Linux kernel, or only AlmaLinux distro suffers from that.
Thanks a lot!
Regards,
Zoltan Balogh
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2024-09-02 15:43 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20240902084335.1e048358@hermes.local \
--to=stephen@networkplumber.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.