All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Hutchings <ben@decadent.org.uk>
To: Chuck Lever <chuck.lever@oracle.com>, Steven Shiau <steven@nchc.org.tw>
Cc: 579397@bugs.debian.org, linux-nfs@vger.kernel.org
Subject: Re: Bug#579397: STAT_FAIL to debian for SM_MON of 192.168.120.254, No canonical hostname found for 192.168.120.254
Date: Sat, 05 Jun 2010 21:29:59 +0100	[thread overview]
Message-ID: <1275769799.2870.107.camel@localhost> (raw)
In-Reply-To: <4C0819C2.2020203@oracle.com>

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

On Thu, 2010-06-03 at 17:08 -0400, Chuck Lever wrote:
> On 05/24/10 11:22 AM, Chuck Lever wrote:
[...]
> > We can probably remove the reverse mapping constraint for presentation
> > addresses. A simple fix might be to change statd_canonical_name() from:
> >
> > freeaddrinfo(ai);
> > if (!result)
> > return NULL;
> >
> > to
> >
> > freeaddrinfo(ai);
> > if (!result)
> > return strdup(hostname);
> >
> > Let me know if this works.
> 
> Any update?  I have a patch ready for nfs-utils to fix this regression, 
> but I need confirmation that it addresses your problem.

Steven originally had this problem, not me.  Steven, do you need me to
build a new package with this change?

Ben.

-- 
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]

  reply	other threads:[~2010-06-05 20:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4BF71C27.7070309@nchc.org.tw>
2010-05-22  1:38 ` Bug#579397: STAT_FAIL to debian for SM_MON of 192.168.120.254, No canonical hostname found for 192.168.120.254 Ben Hutchings
2010-05-24 15:22   ` Chuck Lever
2010-06-03 21:08     ` Chuck Lever
2010-06-05 20:29       ` Ben Hutchings [this message]
2010-06-09 14:41         ` Steven Shiau
2010-07-06 17:05           ` Chuck Lever
2010-08-08  4:59             ` Ben Hutchings
2010-08-08 16:55               ` 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=1275769799.2870.107.camel@localhost \
    --to=ben@decadent.org.uk \
    --cc=579397@bugs.debian.org \
    --cc=chuck.lever@oracle.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=steven@nchc.org.tw \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.