From: Denys Fedoryshchenko <nuclearcat@nuclearcat.com>
To: Linux Kernel Network Developers <netdev@vger.kernel.org>
Subject: kernel panic TPROXY , vanilla 4.7.1
Date: Wed, 17 Aug 2016 17:31:20 +0300 [thread overview]
Message-ID: <627722c51d9ce454dfaf1a79519ceb59@nuclearcat.com> (raw)
Hi!
Tried to run squid on latest kernel, and hit a panic
Sometimes it just shows warning in dmesg (but doesnt work properly)
[ 75.701666] IPv4: Attempt to release TCP socket in state 10
ffff88102d430780
[ 83.866974] squid (2700) used greatest stack depth: 12912 bytes left
[ 87.506644] IPv4: Attempt to release TCP socket in state 10
ffff880078a48780
[ 114.704295] IPv4: Attempt to release TCP socket in state 10
ffff881029f8ad00
I cannot catch yet oops/panic message, netconsole not working.
After triggering warning message 3 times, i am unable to run squid
anymore (without reboot), and in netstat it doesnt show port running.
firewall is:
*mangle
-A PREROUTING -p tcp -m socket -j DIVERT
-A PREROUTING -p tcp -m tcp --dport 80 -i eno1 -j TPROXY --on-port 3129
--on-ip 0.0.0.0 --tproxy-mark 0x1/0x1
-A DIVERT -j MARK --set-xmark 0x1/0xffffffff
-A DIVERT -j ACCEPT
routing
ip rule add fwmark 1 lookup 100
ip route add local default dev eno1 table 100
squid config is default with tproxy option
http_port 3129 tproxy
next reply other threads:[~2016-08-17 14:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-17 14:31 Denys Fedoryshchenko [this message]
2016-08-17 15:42 ` kernel panic TPROXY , vanilla 4.7.1 Eric Dumazet
2016-08-17 16:04 ` Eric Dumazet
2016-08-17 16:44 ` Denys Fedoryshchenko
2016-08-17 16:48 ` Eric Dumazet
2016-08-17 16:56 ` [PATCH net] netfilter: tproxy: properly refcount tcp listeners Eric Dumazet
2016-08-17 22:51 ` Pablo Neira Ayuso
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=627722c51d9ce454dfaf1a79519ceb59@nuclearcat.com \
--to=nuclearcat@nuclearcat.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).