From: David Teigland <teigland@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org
Subject: [GIT PULL] dlm updates for 4.15
Date: Mon, 13 Nov 2017 12:24:18 -0600 [thread overview]
Message-ID: <20171113182418.GD29355@redhat.com> (raw)
Hi Linus,
Please pull dlm updates from tag:
git://git.kernel.org/pub/scm/linux/kernel/git/teigland/linux-dlm.git dlm-4.15
This set focuses, as usual, on fixes to the comms layer.
New testing of the dlm with ocfs2 uncovered a number of
bugs in the TCP connection handling during recovery,
starting, and stopping.
Thanks,
Dave
Bob Peterson (3):
DLM: Eliminate CF_CONNECT_PENDING flag
DLM: Eliminate CF_WRITE_PENDING flag
DLM: Fix saving of NULL callbacks
David Teigland (1):
dlm: remove dlm_send_rcom_lookup_dump
Guoqing Jiang (1):
dlm: recheck kthread_should_stop() before schedule()
tsutomu.owa@toshiba.co.jp (15):
DLM: fix remove save_cb argument from add_sock()
DLM: fix double list_del()
DLM: fix race condition between dlm_send and dlm_recv
DLM: fix to use sock_mutex correctly in xxx_accept_from_sock
DLM: retry rcom when dlm_wait_function is timed out.
DLM: close othercon at send/receive error
DLM: fix race condition between dlm_recoverd_stop and dlm_recoverd
DLM: Reanimate CF_WRITE_PENDING flag
DLM: use CF_CLOSE flag to stop dlm_send correctly
DLM: fix conversion deadlock when DLM_LKF_NODLCKWT flag is set
DLM: fix memory leak in tcp_accept_from_sock()
DLM: fix overflow dlm_cb_seq
DLM: fix to use sk_callback_lock correctly
DLM: fix to reschedule rwork
DLM: fix NULL pointer dereference in send_to_sock()
fs/dlm/ast.c | 2 +
fs/dlm/lock.c | 43 ++++++-----
fs/dlm/lowcomms.c | 218 ++++++++++++++++++++++++++++++++++--------------------
fs/dlm/rcom.c | 26 ++-----
fs/dlm/rcom.h | 1 -
fs/dlm/recover.c | 4 +
fs/dlm/recoverd.c | 16 +++-
7 files changed, 186 insertions(+), 124 deletions(-)
reply other threads:[~2017-11-13 18:24 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20171113182418.GD29355@redhat.com \
--to=teigland@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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