From: Steve Dickson <SteveD@redhat.com>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: linux-nfs@vger.kernel.org
Subject: Re: [PATCH 0/5] Possible fixes for statd / sm-notify / exportfs
Date: Mon, 29 Aug 2011 13:48:26 -0400 [thread overview]
Message-ID: <4E5BD0EA.10802@RedHat.com> (raw)
In-Reply-To: <20110824153024.3138.63294.stgit@matisse.1015granger.net>
On 08/24/2011 11:33 AM, Chuck Lever wrote:
> While working on another fix, I noticed that the complex hostname
> matching logic in statd, exportfs, and sm-notify appears to break with
> the local hostname and IP addresses. I propose the following to
> address this.
>
> ---
>
> Chuck Lever (5):
> sm-notify: sm-notify doesn't handle localhost properly
> exportfs: matchhostname() doesn't handle localhost properly
> statd: statd_matchhostname() doesn't handle localhost properly
> sm-notify: Disable syslog messages when debugging is enabled
> statd: Report count of loaded hosts correctly
>
>
> utils/exportfs/exportfs.c | 34 +++++++++++-
> utils/statd/hostname.c | 55 ++++++++++++++++---
> utils/statd/monitor.c | 2 -
> utils/statd/sm-notify.c | 133 ++++++++++++++++++++++++++++++++++++---------
> 4 files changed, 186 insertions(+), 38 deletions(-)
>
All 5 patches committed...
steved.
prev parent reply other threads:[~2011-08-29 17:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-24 15:33 [PATCH 0/5] Possible fixes for statd / sm-notify / exportfs Chuck Lever
2011-08-24 15:33 ` [PATCH 1/5] statd: Report count of loaded hosts correctly Chuck Lever
2011-08-24 15:34 ` [PATCH 2/5] sm-notify: Disable syslog messages when debugging is enabled Chuck Lever
2011-08-24 15:34 ` [PATCH 3/5] statd: statd_matchhostname() doesn't handle localhost properly Chuck Lever
2011-08-24 15:34 ` [PATCH 4/5] exportfs: matchhostname() " Chuck Lever
2011-08-24 15:34 ` [PATCH 5/5] sm-notify: sm-notify " Chuck Lever
2011-08-29 17:48 ` Steve Dickson [this message]
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=4E5BD0EA.10802@RedHat.com \
--to=steved@redhat.com \
--cc=chuck.lever@oracle.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).