From: Willy Tarreau <w@1wt.eu>
To: Michelle Bies <mimbies@outlook.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
Eric Dumazet <edumazet@google.com>
Subject: Re: TPROXY + Attempt to release TCP socket in state 1
Date: Sat, 9 Jul 2022 08:41:14 +0200 [thread overview]
Message-ID: <20220709064114.GA4860@1wt.eu> (raw)
In-Reply-To: <HE1P193MB01233D583E9A7B1418A77713A8859@HE1P193MB0123.EURP193.PROD.OUTLOOK.COM>
Hi,
On Sat, Jul 09, 2022 at 06:14:14AM +0000, Michelle Bies wrote:
> Hi Eric
> unfortunately, nobody response to my problem :(
> Did I report my problem to the right mailing list?
You sent it only 4 days ago! As you might have noticed you're not the
only one to request help, code reviews or anything that requires time
from only a few people. What progress have you made on your side on
the analysis of this problem in during this time, that you could share
to save precious time to those who are going to help you, and to make
your issue more interesting to analyse than other ones ?
Also, I'm seeing that your kernel is tainted by an out-of-tree module:
> > CPU: 5 PID: 0 Comm: swapper/5 Tainted: GO 5.4.181+ #9
^^
Most likely it's this "xt_geoip" module but it may also be anything
else I have not spotted in your dump. Have you rechecked without it ?
While unlikely to be related, any out-of-tree code must be handled
with extreme care, as their impact on the rest of the kernel remains
mostly unknown, so they're the first ones to disable during
troubleshooting.
> > My current kernel is 5.4 and these are my iptables config:
Please always mention the exact version in reports. I've seen "5.4.181+"
in your dump, which means 5.4.181 plus extra patches. Have you tried
again without them ?
Hoping this helps,
Willy
next prev parent reply other threads:[~2022-07-09 6:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-05 8:52 TPROXY + Attempt to release TCP socket in state 1 Michelle Bies
2022-07-09 6:14 ` Michelle Bies
2022-07-09 6:41 ` Willy Tarreau [this message]
2022-07-09 8:05 ` Eric Dumazet
2022-07-09 8:34 ` Michelle Bies
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=20220709064114.GA4860@1wt.eu \
--to=w@1wt.eu \
--cc=edumazet@google.com \
--cc=mimbies@outlook.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