From: Eric Dumazet <eric.dumazet@gmail.com>
To: Timofey Titovets <nefelim4ag@gmail.com>, netdev@vger.kernel.org
Subject: Re: Possible tcp regression in 4.14.13..26
Date: Tue, 13 Mar 2018 14:45:04 -0700 [thread overview]
Message-ID: <1a119dc3-7bd8-0446-e545-f2af77d76a63@gmail.com> (raw)
In-Reply-To: <CAGqmi77b0HQAX-dg7JKAWEnu+eFtn8GS+5dsj2kO9Xnzcn_tLg@mail.gmail.com>
On 03/13/2018 02:41 PM, Timofey Titovets wrote:
> Hi list,
> We currently upgrade our servers from 4.14.13 to 4.14.26
> And get some problems with random kernel oops by:
> [ 422.081094] BUG: unable to handle kernel NULL pointer dereference
> at 0000000000000038
> [ 422.081254] IP: tcp_push+0x42/0x110
> [ 422.081314] PGD 0 P4D 0
> [ 422.081364] Oops: 0002 [#1] SMP PTI
>
> Currently we assume that this caused by:
> net: tcp: close sock if net namespace is exiting
> [ Upstream commit 4ee806d51176ba7b8ff1efd81f271d7252e03a1d ]
>
> If that can helps we heavy use docker and ceph rbd.
>
> I will write if we get more info or fix that.
>
> Thanks.
>
Can you provide a full stack trace ?
prev parent reply other threads:[~2018-03-13 21:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-13 21:41 Possible tcp regression in 4.14.13..26 Timofey Titovets
2018-03-13 21:45 ` Eric Dumazet [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=1a119dc3-7bd8-0446-e545-f2af77d76a63@gmail.com \
--to=eric.dumazet@gmail.com \
--cc=nefelim4ag@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).