General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Eric Dumazet <eric.dumazet@gmail.com>
To: bloat@lists.bufferbloat.net
Subject: Re: [Bloat] bufferbloat.net server having troubles?
Date: Sat, 31 Mar 2018 17:50:31 -0700	[thread overview]
Message-ID: <efdbeb6f-3c1e-5c95-954c-5f81e2d1bb5f@gmail.com> (raw)
In-Reply-To: <3DCC1B31-2A54-4306-A355-7DBD15184C5F@gmail.com>



On 03/31/2018 12:54 PM, Jonathan Morton wrote:
>> On 31 Mar, 2018, at 10:50 pm, Toke Høiland-Jørgensen <toke@toke.dk> wrote:
>>
>> Yeah, the box running the web server is having some issues with NULL
>> pointer dereferences in tcp_push() in the kernel crashing processes
>> running TCP. Haven't been able to figure out why :/
> 
> Maybe build/install a new kernel and reboot?
> 
> Possibility exists of hardware failure, too.  Less likely, perhaps, but if you don't have ECC...
> 

Nope, known bug on stable kernels.

Please upgrade or downgrade.

$ git log --oneline v4.14.31..v4.14.32  -- net/ipv4/tcp.c
e44c1733059c tcp: purge write queue upon aborting the connection

commit e44c1733059c69868e81f82eb09fcb6bbc492050
Author: Soheil Hassas Yeganeh <soheil@google.com>
Date:   Tue Mar 6 17:15:12 2018 -0500

    tcp: purge write queue upon aborting the connection
    
    
    [ Upstream commit e05836ac07c77dd90377f8c8140bce2a44af5fe7 ]
    
    When the connection is aborted, there is no point in
    keeping the packets on the write queue until the connection
    is closed.
    
    Similar to a27fd7a8ed38 ('tcp: purge write queue upon RST'),
    this is essential for a correct MSG_ZEROCOPY implementation,
    because userspace cannot call close(fd) before receiving
    zerocopy signals even when the connection is aborted.
    
    Fixes: f214f915e7db ("tcp: enable MSG_ZEROCOPY")
    Signed-off-by: Soheil Hassas Yeganeh <soheil@google.com>
    Signed-off-by: Neal Cardwell <ncardwell@google.com>
    Reviewed-by: Eric Dumazet <edumazet@google.com>
    Signed-off-by: Yuchung Cheng <ycheng@google.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>



  reply	other threads:[~2018-04-01  0:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-31 18:26 Rich Brown
2018-03-31 19:50 ` Toke Høiland-Jørgensen
2018-03-31 19:54   ` Jonathan Morton
2018-04-01  0:50     ` Eric Dumazet [this message]
2018-04-01 15:45       ` Toke Høiland-Jørgensen

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

  List information: https://lists.bufferbloat.net/postorius/lists/bloat.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=efdbeb6f-3c1e-5c95-954c-5f81e2d1bb5f@gmail.com \
    --to=eric.dumazet@gmail.com \
    --cc=bloat@lists.bufferbloat.net \
    /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