From: Chuck Lever <chuck.lever@oracle.com>
To: steved@redhat.com
Cc: neilb@suse.de, linux-nfs@vger.kernel.org
Subject: [PATCH 0/2] nfs-utils: fix check_netgroup()
Date: Wed, 04 Aug 2010 13:12:48 -0400 [thread overview]
Message-ID: <20100804171036.2657.8657.stgit@seurat.1015granger.net> (raw)
This is the patch I posted yesterday, split into two smaller changes
and with Neil's comments addressed. This is reviewed and compile-
tested, but needs testing by someone who has real netgroup test cases,
which I don't have.
Steve, this fix should be included in the upcoming release of
nfs-utils (after appropriate testing, of course).
---
Chuck Lever (2):
libexport: Fix IP address check in check_netgroup()
libexport: Add a common exit label to check_netgroup()
support/export/client.c | 39 +++++++++++++++++++++++++++++----------
1 files changed, 29 insertions(+), 10 deletions(-)
--
Chuck Lever
next reply other threads:[~2010-08-04 17:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-04 17:12 Chuck Lever [this message]
2010-08-04 17:13 ` [PATCH 1/2] libexport: Add a common exit label to check_netgroup() Chuck Lever
2010-08-04 17:13 ` [PATCH 2/2] libexport: Fix IP address check in check_netgroup() Chuck Lever
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=20100804171036.2657.8657.stgit@seurat.1015granger.net \
--to=chuck.lever@oracle.com \
--cc=linux-nfs@vger.kernel.org \
--cc=neilb@suse.de \
--cc=steved@redhat.com \
/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).