public inbox for linux-cifs@vger.kernel.org
 help / color / mirror / Atom feed
From: Samuel Cabrero <scabrero@suse.de>
To: linux-cifs@vger.kernel.org
Subject: [PATCH v3 00/11] Witness protocol support for transparent failover
Date: Fri, 30 Oct 2020 12:51:59 +0100	[thread overview]
Message-ID: <20201030115210.8888-1-scabrero@suse.de> (raw)

Changes from v2:
  * Fix 'no previous prototype' kernel test robot warning in
    fs/cifs/netlink.c

Changes from v1:
  * Update SPDX header in user space API files to LGPL-2.1+ with
    Linux-syscall-note

[PATCH v3 01/11] cifs: Make extract_hostname function public
[PATCH v3 02/11] cifs: Make extract_sharename function public
[PATCH v3 03/11] cifs: Register generic netlink family
[PATCH v3 04/11] cifs: add witness mount option and data structs
[PATCH v3 05/11] cifs: Send witness register and unregister commands
[PATCH v3 06/11] cifs: Set witness notification handler for messages
[PATCH v3 07/11] cifs: Add witness information to debug data dump
[PATCH v3 08/11] cifs: Send witness register messages to userspace
[PATCH v3 09/11] cifs: Simplify reconnect code when dfs upcall is
[PATCH v3 10/11] cifs: Handle witness client move notification
[PATCH v3 11/11] cifs: Handle witness share moved notification

 fs/cifs/Kconfig                        |  11 +
 fs/cifs/Makefile                       |   2 +
 fs/cifs/cache.c                        |  24 -
 fs/cifs/cifs_debug.c                   |  13 +
 fs/cifs/cifs_swn.c                     | 723 ++++++++++++++++++++++++
 fs/cifs/cifs_swn.h                     |  25 +
 fs/cifs/cifsfs.c                       |  22 +-
 fs/cifs/cifsglob.h                     |   8 +
 fs/cifs/cifsproto.h                    |   2 +
 fs/cifs/connect.c                      | 141 +++--
 fs/cifs/fscache.c                      |   1 +
 fs/cifs/fscache.h                      |   1 -
 fs/cifs/misc.c                         |  56 ++
 fs/cifs/netlink.c                      |  89 +++
 fs/cifs/netlink.h                      |  16 +
 include/uapi/linux/cifs/cifs_netlink.h |  63 +++
 16 files changed, 1118 insertions(+), 79 deletions(-)


             reply	other threads:[~2020-10-30 11:52 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-30 11:51 Samuel Cabrero [this message]
2020-10-30 11:52 ` [PATCH v3 01/11] cifs: Make extract_hostname function public Samuel Cabrero
2020-10-30 11:52 ` [PATCH v3 02/11] cifs: Make extract_sharename " Samuel Cabrero
2020-10-30 11:52 ` [PATCH v3 03/11] cifs: Register generic netlink family Samuel Cabrero
2020-10-30 11:52 ` [PATCH v3 04/11] cifs: add witness mount option and data structs Samuel Cabrero
2020-10-30 11:52 ` [PATCH v3 05/11] cifs: Send witness register and unregister commands to userspace daemon Samuel Cabrero
2020-10-30 11:52 ` [PATCH v3 06/11] cifs: Set witness notification handler for messages from " Samuel Cabrero
2020-10-30 11:52 ` [PATCH v3 07/11] cifs: Add witness information to debug data dump Samuel Cabrero
2020-10-30 11:52 ` [PATCH v3 08/11] cifs: Send witness register messages to userspace daemon in echo task Samuel Cabrero
2020-10-30 11:52 ` [PATCH v3 09/11] cifs: Simplify reconnect code when dfs upcall is enabled Samuel Cabrero
2020-10-30 11:52 ` [PATCH v3 10/11] cifs: Handle witness client move notification Samuel Cabrero
2020-10-30 11:52 ` [PATCH v3 11/11] cifs: Handle witness share moved notification Samuel Cabrero

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=20201030115210.8888-1-scabrero@suse.de \
    --to=scabrero@suse.de \
    --cc=linux-cifs@vger.kernel.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