From: NeilBrown <neilb@suse.de>
To: "J. Bruce Fields" <bfields@fieldses.org>,
Chuck Lever <chuck.lever@oracle.com>,
kircherlike@outlook.com,
Stephen Hemminger <stephen@networkplumber.org>
Cc: linux-nfs@vger.kernel.org
Subject: [PATCH 0/3 - V2] SUNRPC/svc: fix gss flavour registration problems.
Date: Fri, 22 May 2020 12:01:32 +1000 [thread overview]
Message-ID: <159011265914.29107.13764997801950546826.stgit@noble> (raw)
In this second version:
- #include added in first patch so new function is declare both where
it is defined and where it is used
- doxy comment added for auth_domain_cleanup()
- pr_warn() used instead of printk
- 'svc:' used as message prefix
- EADDRINUSE returned instead of EALREADY - I think it is slightly more
accurate.
- 'cc: stable' dropped for first patch. Bug goes back before 'git' so
no 'Fixes:'
- minor code revision
Thanks,
NeilBrown
---
NeilBrown (3):
sunrpc: check that domain table is empty at module unload.
sunrpc: svcauth_gss_register_pseudoflavor must reject duplicate registrations.
sunrpc: clean up properly in gss_mech_unregister()
include/linux/sunrpc/gss_api.h | 1 +
include/linux/sunrpc/svcauth_gss.h | 3 ++-
net/sunrpc/auth_gss/gss_mech_switch.c | 12 +++++++++---
net/sunrpc/auth_gss/svcauth_gss.c | 18 ++++++++++--------
net/sunrpc/sunrpc.h | 1 +
net/sunrpc/sunrpc_syms.c | 2 ++
net/sunrpc/svcauth.c | 25 +++++++++++++++++++++++++
7 files changed, 50 insertions(+), 12 deletions(-)
--
Signature
next reply other threads:[~2020-05-22 2:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-22 2:01 NeilBrown [this message]
2020-05-22 2:01 ` [PATCH 1/3] sunrpc: check that domain table is empty at module unload NeilBrown
2020-05-22 2:01 ` [PATCH 3/3] sunrpc: clean up properly in gss_mech_unregister() NeilBrown
2020-05-26 0:23 ` Sasha Levin
2020-05-26 0:50 ` NeilBrown
2020-05-22 2:01 ` [PATCH 2/3] sunrpc: svcauth_gss_register_pseudoflavor must reject duplicate registrations NeilBrown
2020-05-28 22:26 ` [PATCH 0/3 - V2] SUNRPC/svc: fix gss flavour registration problems J. Bruce Fields
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=159011265914.29107.13764997801950546826.stgit@noble \
--to=neilb@suse.de \
--cc=bfields@fieldses.org \
--cc=chuck.lever@oracle.com \
--cc=kircherlike@outlook.com \
--cc=linux-nfs@vger.kernel.org \
--cc=stephen@networkplumber.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;
as well as URLs for NNTP newsgroup(s).