From: Stephen Hemminger <stephen@networkplumber.org>
To: Adam Mitchell <adamhmitchell@gmail.com>
Cc: netdev@vger.kernel.org
Subject: Re: Kernel warnings from tcp.c
Date: Wed, 29 Aug 2018 12:35:40 -0700 [thread overview]
Message-ID: <20180829123540.09c167b6@xeon-e3> (raw)
In-Reply-To: <CAEXp4ork9mZ9pY_o5LnG87tL5aRPLfpr1ZZ=p7qpZMJCKi-enA@mail.gmail.com>
On Wed, 29 Aug 2018 14:38:38 -0400
Adam Mitchell <adamhmitchell@gmail.com> wrote:
> Anyone with experience in tcp.c have an idea what's causing this on
> our busy database server? Comes from this macro at line 2278:
> WARN_ON(sock_owned_by_user(sk));
>
>
> [726780.788201] WARNING: CPU: 15 PID: 52245 at net/ipv4/tcp.c:2278
> tcp_close+0x40f/0x430
>
> [726780.794947] Modules linked in: binfmt_misc nf_conntrack_netlink
> nfnetlink_queue tcp_diag inet_diag isofs ip6table_mangle ip6table_raw
> ip6table_nat nf_nat_ipv6 iptable_security xt_CT iptable_raw
> iptable_nat nf_nat_ipv4 nf_nat iptable_mangle xt_pkttype xt_NFLOG
> nfnetlink_log xt_u32 xt_multiport xt_set xt_conntrack
> ip_set_hash_netport ip_set_hash_ipport ip_set_hash_net ip_set_hash_ip
> ip_set nfnetlink nf_conntrack_proto_gre nf_conntrack_ipv6
> nf_defrag_ipv6 ip6table_filter ip6_tables xt_LOG nf_conntrack_tftp
> nf_conntrack_ftp nf_conntrack_ipv4 nf_defrag_ipv4 nf_conntrack
> iptable_filter zfs(PO) zunicode(PO) zavl(PO) icp(PO) sb_edac
> intel_powerclamp crct10dif_pclmul crc32_pclmul ghash_clmulni_intel
> pcbc aesni_intel crypto_simd glue_helper cryptd cirrus snd_seq
> zcommon(PO) ttm intel_rapl_perf snd_seq_device
> [726780.848696] drm_kms_helper znvpair(PO) snd_pcm snd_timer spl(O)
> drm snd soundcore syscopyarea sysfillrect pcspkr sysimgblt input_leds
> fb_sys_fops i2c_piix4 ip_tables xfs libcrc32c ata_generic pata_acpi
> ata_piix xen_blkfront crc32c_intel libata ena(O) serio_raw floppy
> sunrpc
> [726780.863916] CPU: 15 PID: 52245 Comm: mysqld Tainted: P W O
> 4.16.13-1.el7.elrepo.x86_64 #1
>
Sorry, you have a tainted kernel with modules that are not upstream
therefore don't expect any support from kernel community
prev parent reply other threads:[~2018-08-29 23:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-29 18:38 Kernel warnings from tcp.c Adam Mitchell
2018-08-29 19:35 ` Stephen Hemminger [this message]
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=20180829123540.09c167b6@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=adamhmitchell@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).