From: NeilBrown <neilb@suse.com>
To: Steve Dickson <SteveD@redhat.com>
Cc: Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: [PATCH 0/2] Revise handling of some mount errors.
Date: Wed, 30 Nov 2016 11:53:51 +1100 [thread overview]
Message-ID: <148046718451.21092.10685567606499960786.stgit@noble> (raw)
These two patches improve the error messages reported when mount.nfs
fails, and reduces the timeout for some errors which are unlikely to
persist.
---
NeilBrown (2):
mount: don't hide temporary error code on timeout.
mount: take history into account when assessing if an error is permanent.
utils/mount/stropts.c | 31 +++++++++++++++++++++++--------
1 file changed, 23 insertions(+), 8 deletions(-)
--
Signature
next reply other threads:[~2016-11-30 0:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-30 0:53 NeilBrown [this message]
2016-11-30 0:53 ` [PATCH 1/2] mount: don't hide temporary error code on timeout NeilBrown
2016-11-30 0:53 ` [PATCH 2/2] mount: take history into account when assessing if an error is permanent NeilBrown
2016-12-01 19:36 ` Steve Dickson
2016-12-01 22:09 ` NeilBrown
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=148046718451.21092.10685567606499960786.stgit@noble \
--to=neilb@suse.com \
--cc=SteveD@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