From: Doug Nazar <nazard@nazar.ca>
To: linux-nfs@vger.kernel.org
Subject: [PATCH 00/11] nfs-utils: Misc cleanups & fixes
Date: Sat, 18 Jul 2020 05:24:10 -0400 [thread overview]
Message-ID: <20200718092421.31691-1-nazard@nazar.ca> (raw)
Again, here are various cleanups and fixes. Nothing too major, although
a couple valgrind finds.
I've left out the printf patch for now, pending further discussion.
Thanks,
Doug
Doug Nazar (11):
Add error handling to libevent allocations.
gssd: Fix cccache buffer size
gssd: Fix handling of failed allocations
gssd: srchost should never be *
xlog: Reorganize xlog_backend() to work around -Wmaybe-uninitialized
nfsdcld: Add graceful exit handling and resource cleanup
nfsdcld: Don't copy more data than exists in column
svcgssd: Convert to using libevent
nfsidmap: Add support to cleanup resources on exit
svcgssd: Cleanup global resources on exit
svcgssd: Wait for nullrpc channel if not available
support/nfs/xlog.c | 41 ++++----
support/nfsidmap/libnfsidmap.c | 13 +++
support/nfsidmap/nfsidmap.h | 1 +
support/nfsidmap/nfsidmap_common.c | 11 ++-
support/nfsidmap/nfsidmap_private.h | 1 +
support/nfsidmap/nss.c | 8 ++
utils/gssd/Makefile.am | 2 +-
utils/gssd/gss_names.c | 6 +-
utils/gssd/gss_util.c | 6 ++
utils/gssd/gss_util.h | 1 +
utils/gssd/gssd.c | 37 +++++--
utils/gssd/krb5_util.c | 12 +--
utils/gssd/svcgssd.c | 143 ++++++++++++++++++++++++++--
utils/gssd/svcgssd.h | 3 +-
utils/gssd/svcgssd_krb5.c | 21 ++--
utils/gssd/svcgssd_krb5.h | 1 +
utils/gssd/svcgssd_main_loop.c | 94 ------------------
utils/gssd/svcgssd_proc.c | 15 +--
utils/idmapd/idmapd.c | 32 +++++++
utils/nfsdcld/nfsdcld.c | 50 +++++++++-
utils/nfsdcld/sqlite.c | 33 +++++--
utils/nfsdcld/sqlite.h | 1 +
22 files changed, 358 insertions(+), 174 deletions(-)
delete mode 100644 utils/gssd/svcgssd_main_loop.c
--
2.26.2
next reply other threads:[~2020-07-18 9:24 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-18 9:24 Doug Nazar [this message]
2020-07-18 9:24 ` [PATCH 01/11] Add error handling to libevent allocations Doug Nazar
2020-07-18 9:24 ` [PATCH 02/11] gssd: Fix cccache buffer size Doug Nazar
2020-07-20 14:43 ` Steve Dickson
2020-07-20 15:41 ` Doug Nazar
2020-07-18 9:24 ` [PATCH 03/11] gssd: Fix handling of failed allocations Doug Nazar
2020-07-18 9:24 ` [PATCH 04/11] gssd: srchost should never be * Doug Nazar
2020-07-18 9:24 ` [PATCH 05/11] xlog: Reorganize xlog_backend() to work around -Wmaybe-uninitialized Doug Nazar
2020-07-18 9:24 ` [PATCH 06/11] nfsdcld: Add graceful exit handling and resource cleanup Doug Nazar
2020-07-18 9:24 ` [PATCH 07/11] nfsdcld: Don't copy more data than exists in column Doug Nazar
2020-07-18 9:24 ` [PATCH 08/11] svcgssd: Convert to using libevent Doug Nazar
2020-07-18 9:24 ` [PATCH 09/11] nfsidmap: Add support to cleanup resources on exit Doug Nazar
2020-07-20 15:49 ` Steve Dickson
2020-07-20 15:58 ` Doug Nazar
2020-07-20 17:31 ` Steve Dickson
2020-07-18 9:24 ` [PATCH 10/11] svcgssd: Cleanup global " Doug Nazar
2020-07-18 9:24 ` [PATCH 11/11] svcgssd: Wait for nullrpc channel if not available Doug Nazar
2020-07-18 15:55 ` J. Bruce Fields
2020-07-18 18:07 ` Doug Nazar
2020-07-27 14:42 ` [PATCH 00/11] nfs-utils: Misc cleanups & fixes Steve Dickson
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=20200718092421.31691-1-nazard@nazar.ca \
--to=nazard@nazar.ca \
--cc=linux-nfs@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;
as well as URLs for NNTP newsgroup(s).