Linux NFS development
 help / color / mirror / Atom feed
From: NeilBrown <neilb@suse.com>
To: Steve Dickson <SteveD@redhat.com>
Cc: linux-nfs@vger.kernel.org, "J. Bruce Fields" <bfields@redhat.com>
Subject: [PATCH 0/4] Assorted nfs-utils patches.
Date: Wed, 21 Dec 2016 11:19:13 +1100	[thread overview]
Message-ID: <148227940052.31345.1974080582264239934.stgit@noble> (raw)

First two relate to /etc/nfs.conf and nfsd.
Second to help make sure that nfs things don't cause
problem when they are started early because various
other services are available (most of that is already
fixed, these are just dribs and drabs).

At some stage I want to convert everything to use the same logging
infrastructure, but that doesn't need to happen before the pending
release.

Thanks,
NeilBrown


---

NeilBrown (4):
      nfsd: fix setting of minor version from config file.
      nfsd: Do not permit manipulation of NFSv4.0, e.g. "-N 4.0"
      nfs-server-generator: avoid using syslog
      mountd: delay reading etab until first request arrives.


 systemd/nfs-server-generator.c |    3 +++
 utils/mountd/mountd.c          |    2 --
 utils/nfsd/nfsd.c              |   20 ++++++++++++++++----
 utils/nfsd/nfsd.man            |   10 +++++-----
 4 files changed, 24 insertions(+), 11 deletions(-)

--
Signature


             reply	other threads:[~2016-12-21  0:19 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-21  0:19 NeilBrown [this message]
2016-12-21  0:19 ` [PATCH 1/4] nfsd: fix setting of minor version from config file NeilBrown
2016-12-21  0:19 ` [PATCH 2/4] nfsd: Do not permit manipulation of NFSv4.0, e.g. "-N 4.0" NeilBrown
2016-12-21  0:19 ` [PATCH 4/4] mountd: delay reading etab until first request arrives NeilBrown
2016-12-22 20:35   ` J. Bruce Fields
2016-12-22 23:16     ` NeilBrown
2016-12-23  0:35       ` J. Bruce Fields
2016-12-21  0:19 ` [PATCH 3/4] nfs-server-generator: avoid using syslog NeilBrown
2017-01-04 16:56 ` [PATCH 0/4] Assorted nfs-utils patches 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=148227940052.31345.1974080582264239934.stgit@noble \
    --to=neilb@suse.com \
    --cc=SteveD@redhat.com \
    --cc=bfields@redhat.com \
    --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