From: David Miller <davem@davemloft.net>
To: sowmini.varadhan@oracle.com
Cc: netdev@vger.kernel.org, rds-devel@oss.oracle.com,
ajaykumar.hotchandani@oracle.com, santosh.shilimkar@oracle.com
Subject: Re: [PATCH net 0/2] RDS: TCP: connection spamming fixes
Date: Fri, 20 May 2016 19:20:32 -0400 (EDT) [thread overview]
Message-ID: <20160520.192032.1207007536147387597.davem@davemloft.net> (raw)
In-Reply-To: <cover.1463579486.git.sowmini.varadhan@oracle.com>
From: Sowmini Varadhan <sowmini.varadhan@oracle.com>
Date: Wed, 18 May 2016 10:06:22 -0700
> We have been testing the RDS-TCP code with a connection spammer
> that sends incoming SYNs to the RDS listen port well after
> an rds-tcp connection has been established, and found a few
> race-windows that are fixed by this patch series.
>
> Patch 1 avoids a null pointer deref when an incoming SYN
> shows up when a netns is being dismantled, or when the
> rds-tcp module is being unloaded.
>
> Patch 2 addresses the case when a SYN is received after the
> connection arbitration algorithm has converged: the incoming
> SYN should not needlessly quiesce the transmit path, and it
> should not result in needless TCP connection resets due to
> re-execution of the connection arbitration logic.
Series applied, thanks.
prev parent reply other threads:[~2016-05-20 23:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-18 17:06 [PATCH net 0/2] RDS: TCP: connection spamming fixes Sowmini Varadhan
2016-05-18 17:06 ` [PATCH net 1/2] RDS: TCP: rds_tcp_accept_worker() must exit gracefully when terminating rds-tcp Sowmini Varadhan
2016-05-18 18:33 ` Santosh Shilimkar
2016-05-18 17:06 ` [PATCH net 2/2] RDS: TCP: Avoid rds connection churn from rogue SYNs Sowmini Varadhan
2016-05-18 18:33 ` Santosh Shilimkar
2016-05-20 23:20 ` David Miller [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=20160520.192032.1207007536147387597.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=ajaykumar.hotchandani@oracle.com \
--cc=netdev@vger.kernel.org \
--cc=rds-devel@oss.oracle.com \
--cc=santosh.shilimkar@oracle.com \
--cc=sowmini.varadhan@oracle.com \
/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).