From: Steve Dickson <steved@redhat.com>
To: Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: [PATCH 0/2] mountd.nfs: Better error diagnostics for the mount command
Date: Wed, 2 Jun 2010 09:41:22 -0400 [thread overview]
Message-ID: <1275486084-23899-1-git-send-email-steved@redhat.com> (raw)
The following two patches add better error diagnostics when
invalid protocol version are given and when the network protocol
can not be determined.
Steve Dickson (2):
mount.nfs: silently fails with bad version arguments
mount.nfs: silently fails when the network protocol is not found
utils/mount/network.c | 21 +++++++++++++++++++--
utils/mount/stropts.c | 16 +++++++++++-----
2 files changed, 30 insertions(+), 7 deletions(-)
next reply other threads:[~2010-06-02 14:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-02 13:41 Steve Dickson [this message]
2010-06-02 13:41 ` [PATCH 1/2] mount.nfs: silently fails with bad version arguments Steve Dickson
2010-06-02 21:34 ` Chuck Lever
2010-06-03 12:11 ` Steve Dickson
[not found] ` <4C079BE8.5010509-AfCzQyP5zfLQT0dZR+AlfA@public.gmane.org>
2010-06-03 12:32 ` Steve Dickson
2010-06-02 13:41 ` [PATCH 2/2] mount.nfs: silently fails when the network protocol is not found Steve Dickson
2010-06-02 21:34 ` Chuck Lever
2010-06-03 12:52 ` 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=1275486084-23899-1-git-send-email-steved@redhat.com \
--to=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;
as well as URLs for NNTP newsgroup(s).