public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Subject: [PATCH 1/4] nfs: Update to 2.5.3
Date: Mon, 22 Mar 2021 08:28:27 +0100	[thread overview]
Message-ID: <20210322072827.1456-1-adolf.belka@ipfire.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 3830 bytes --]

- Update from 2.5.1 to 2.5.3
- No update to rootfile required
- Changelog
   Changelog for each version has around 500 lines so there is too much to
    put here. The full change logs for each version can be found at
    https://sourceforge.net/projects/nfs/files/nfs-utils/
   Two bug fixes in 2.5.2 and four in 2.5.3 as follows
    Author: Steve Dickson <steved(a)redhat.com>
    Date:   Tue Feb 2 11:02:47 2021 -0500
      mount: fix parsing of default options
      A recent patch to change configfile.c to use parse_opt.c contained code
      which was intended to remove all "default*" options from the list before
      that could be passed to the kernel.  This code didn't work, so default*
      options WERE passed to the kernel, and the kernel complained and failed
      the mount attempt.
      A more recent patch attempted to fix this by not including the
      "default*" options in the option list at all.  This resulting in
      global-default defaults over-riding per-mount or per-server defaults.
      This patch reverse the "more recent" patch, and fixes the original patch
      by providing correct code to remove all "default*" options before the
      kernel can see them.
       Fixes: 88c22f924f1b ("mount: convert configfile.c to use parse_opt.c")
       Fixes: 8142542bda28 ("mount: parse default values correctly")
    Author: Steve Dickson <steved(a)redhat.com>
    Date:   Wed Jan 6 13:12:12 2021 -0500
      mount: parse default values correctly
      Commit 88c22f92 converted the configfile.c routines
      to use the parse_opt interfaces which broke how
      default values from nfsmount.conf are managed.
      Default values can not be added to the mount string
      handed to the kernel. They must be interpreted into
      the correct mount options then passed to the kernel.
       Fixes: https://bugzilla.redhat.com/show_bug.cgi?id=1912877
    Author: Steve Dickson <steved(a)redhat.com>
    Date:   Mon Nov 9 14:34:15 2020 -0500
      nfs-v4client.target: NFSv4 only client target.
      To allow v4 only clients, create an systemd
      nfs-client target that does not "Wants" a
      rpc-statd notify
       Fixes: https://bugzilla.redhat.com/show_bug.cgi?id=1886634
    Author: Steve Dickson <steved(a)redhat.com>
    Date:   Fri Sep 4 14:15:53 2020 -0400
      rpc.idmapd: Do not free config variables
      Commit 93e8f092e added a conf_cleanup() call to clean
      up memory after the config file was parsed. It turns
      out that memory still needed and it is not very much
      so the call is removed.
       Fixes: https://bugzilla.redhat.com/show_bug.cgi?id=1873965
    Author: Steve Dickson <steved(a)redhat.com>
    Date:   Wed Aug 5 14:59:23 2020 -0400
      rpc.idmapd: Turn down the verbosity in flush_inotify()
      Commit 27a8e146 introduce a debugging message
      that was not cover by a check if verbose
      is set, which cause a large number of message
      to be logged on every kerberos mount
       Fixes: https://bugzilla.redhat.com/show_bug.cgi?id=1867172

Signed-off-by: Adolf Belka <adolf.belka(a)ipfire.org>
---
 lfs/nfs | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/lfs/nfs b/lfs/nfs
index 3e2f56b7e..55accfb28 100644
--- a/lfs/nfs
+++ b/lfs/nfs
@@ -24,7 +24,7 @@
 
 include Config
 
-VER        = 2.5.1
+VER        = 2.5.3
 
 THISAPP    = nfs-utils-$(VER)
 DL_FILE    = $(THISAPP).tar.xz
@@ -32,7 +32,7 @@ DL_FROM    = $(URL_IPFIRE)
 DIR_APP    = $(DIR_SRC)/$(THISAPP)
 TARGET     = $(DIR_INFO)/$(THISAPP)
 PROG       = nfs
-PAK_VER    = 14
+PAK_VER    = 15
 
 DEPS       = libnfsidmap rpcbind
 
@@ -44,7 +44,7 @@ objects = $(DL_FILE)
 
 $(DL_FILE) = $(DL_FROM)/$(DL_FILE)
 
-$(DL_FILE)_MD5 = d14294d5efcd9aada28f4dab871a44a6
+$(DL_FILE)_MD5 = dd8100f51bf838f2a396c86163c9a0e3
 
 install : $(TARGET)
 
-- 
2.31.0


                 reply	other threads:[~2021-03-22  7:28 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=20210322072827.1456-1-adolf.belka@ipfire.org \
    --to=adolf.belka@ipfire.org \
    --cc=development@lists.ipfire.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