From: Sowmini Varadhan <sowmini.varadhan@oracle.com>
To: sowmini.varadhan@oracle.com, dvyukov@google.com,
santosh.shilimkar@oracle.com, davem@davemloft.net,
netdev@vger.kernel.org
Cc: syzkaller@googlegroups.com, rds-devel@oss.oracle.com
Subject: [PATCH net 0/3] rds: tcp: fix various rds-tcp issues during netns create/delete sequences
Date: Sat, 4 Mar 2017 08:57:32 -0800 [thread overview]
Message-ID: <cover.1488645926.git.sowmini.varadhan@oracle.com> (raw)
Dmitry Vyukov reported some syszkaller panics during netns deletion.
While I have not been able to reproduce those exact panics, my attempts
to do so uncovered a few other problems, which are fixed patch 2 and
patch 3 of this patch series. In addition, as mentioned in,
https://www.spinics.net/lists/netdev/msg422997.html
code-inspection points that the rds_connection needs to take an explicit
refcnt on the struct net so that it is held down until all cleanup is
completed for netns removal, and this is fixed by patch1.
The following scripts were run concurrently to uncover/test patch{2, 3}
while simultaneously running rds-ping to 12.0.0.18 from another system:
# cat del.rds
while [ 1 ]; do
modprobe rds_tcp
modprobe -r rds-tcp
done
# cat del.netns
while [ 1 ]; do
ip netns delete blue
ip netns add blue
ip link add link eth1 address a:b:c:d:e:f blue0 type macvlan
ip link set blue0 netns blue
ip netns exec blue ip addr add 12.0.0.18/24 dev blue0
ip netns exec blue ifconfig blue0 up
sleep 3;
done
Sowmini Varadhan (3):
rds: tcp: Take explicit refcounts on struct net
rds: tcp: Reorder initialization sequence in rds_tcp_init to avoid
races
rds: tcp: Sequence teardown of listen and acceptor sockets to avoid
races
net/rds/connection.c | 1 +
net/rds/rds.h | 6 +++---
net/rds/tcp.c | 38 +++++++++++++++++++++-----------------
net/rds/tcp.h | 2 +-
net/rds/tcp_listen.c | 9 +++++++--
5 files changed, 33 insertions(+), 23 deletions(-)
next reply other threads:[~2017-03-05 12:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-04 16:57 Sowmini Varadhan [this message]
2017-03-04 16:57 ` [PATCH net 1/3] rds: tcp: Take explicit refcounts on struct net Sowmini Varadhan
2017-03-04 16:57 ` [PATCH net 2/3] rds: tcp: Reorder initialization sequence in rds_tcp_init to avoid races Sowmini Varadhan
2017-03-04 16:57 ` [PATCH net 3/3] rds: tcp: Sequence teardown of listen and acceptor sockets " Sowmini Varadhan
2017-03-07 1:04 ` [PATCH net 0/3] rds: tcp: fix various rds-tcp issues during netns create/delete sequences santosh.shilimkar
2017-03-07 8:28 ` Dmitry Vyukov
2017-03-07 16:29 ` Santosh Shilimkar
2017-03-07 22:10 ` David Miller
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=cover.1488645926.git.sowmini.varadhan@oracle.com \
--to=sowmini.varadhan@oracle.com \
--cc=davem@davemloft.net \
--cc=dvyukov@google.com \
--cc=netdev@vger.kernel.org \
--cc=rds-devel@oss.oracle.com \
--cc=santosh.shilimkar@oracle.com \
--cc=syzkaller@googlegroups.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).