From: Ursula Braun <ubraun@linux.ibm.com>
To: davem@davemloft.net
Cc: netdev@vger.kernel.org, linux-s390@vger.kernel.org,
schwidefsky@de.ibm.com, heiko.carstens@de.ibm.com,
raspl@linux.ibm.com, ubraun@linux.ibm.com
Subject: [PATCH net-next 0/4] patches 2018-05-23
Date: Wed, 23 May 2018 16:38:08 +0200 [thread overview]
Message-ID: <20180523143812.25824-1-ubraun@linux.ibm.com> (raw)
Dave,
here are more smc-patches for net-next:
Patch 1 fixes an ioctl problem detected by syzbot.
Patch 2 improves smc_lgr_list locking in case of abnormal link
group termination. If you want to receive a version for the net-tree,
please let me know. It would look somewhat different, since the port
terminate code has been moved to smc_core.c on net-next.
Patch 3 enables SMC to deal with urgent data.
Patch 4 is a minor improvement to avoid out-of-sync linkgroups
between 2 peers.
Thanks, Ursula
Hans Wippel (1):
net/smc: lock smc_lgr_list in port_terminate()
Stefan Raspl (1):
net/smc: urgent data support
Ursula Braun (2):
net/smc: return 0 for ioctl calls in states INIT and CLOSED
net/smc: longer delay when freeing client link groups
net/smc/af_smc.c | 42 ++++++++++++++++---
net/smc/smc.h | 15 +++++++
net/smc/smc_cdc.c | 44 ++++++++++++++++++--
net/smc/smc_cdc.h | 13 ++++++
net/smc/smc_core.c | 19 +++++++--
net/smc/smc_rx.c | 120 +++++++++++++++++++++++++++++++++++++++++++++++------
net/smc/smc_tx.c | 55 ++++++++++++++++--------
net/smc/smc_tx.h | 2 +-
8 files changed, 267 insertions(+), 43 deletions(-)
--
2.16.3
next reply other threads:[~2018-05-23 14:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-23 14:38 Ursula Braun [this message]
2018-05-23 14:38 ` [PATCH net-next 1/4] net/smc: return 0 for ioctl calls in states INIT and CLOSED Ursula Braun
2018-05-23 14:38 ` [PATCH net-next 2/4] net/smc: lock smc_lgr_list in port_terminate() Ursula Braun
2018-05-23 14:38 ` [PATCH net-next 3/4] net/smc: urgent data support Ursula Braun
2018-05-23 14:38 ` [PATCH net-next 4/4] net/smc: longer delay when freeing client link groups Ursula Braun
2018-05-23 20:02 ` [PATCH net-next 0/4] patches 2018-05-23 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=20180523143812.25824-1-ubraun@linux.ibm.com \
--to=ubraun@linux.ibm.com \
--cc=davem@davemloft.net \
--cc=heiko.carstens@de.ibm.com \
--cc=linux-s390@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=raspl@linux.ibm.com \
--cc=schwidefsky@de.ibm.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