Linux NFS development
 help / color / mirror / Atom feed
From: Neil Brown <neilb@suse.de>
To: Steve Dickson <SteveD@redhat.com>
Cc: chucklever@gmail.com, linux-nfs@vger.kernel.org
Subject: Re: [PATCH] sm-notify: perform DNS lookup in the background.
Date: Thu, 17 Jul 2008 12:41:40 +1000	[thread overview]
Message-ID: <18558.45412.19541.657376@notabene.brown> (raw)
In-Reply-To: message from Steve Dickson on Wednesday July 16

On Wednesday July 16, SteveD@redhat.com wrote:
> 
> > 
> > Arguably it would be cleaner architecturally if the DNS lookup were in
> > notify_host().  Since doing it in notify() means you will be looking
> > up these addresses on retries, maybe the host_lookup() call should be
> > integrated into the "If we retransmitted 4 times" logic.  That would
> > be an opportunity to fix the addrinfo leak in there.

What addrinfo leak is that?

> > 
> > [Note that freeaddrinfo(3) simply walks the list of addrinfo
> > structures and frees them.  By setting ai_next to NULL in some of the
> > addrinfo structures, sm-notify is orphaning them -- freeaddrinfo(3)
> > will never find them].
> > 

I assume we are talking about the code in notify_host in the
  if (host->retries >= 4) {
branch.

What the code is doing is taking the first addrinfo from the host->ai
list, and moving it to the end - effectively rotating the list.
This shouldn't change what freeaddrinfo will do.

One of us is missing something.
> 
> 
> I believe the following patch address those minor comments... true?

Except for:

> @@ -349,7 +364,6 @@ notify_host(int sock, struct nsm_host *host)
>  		while ( *next )
>  			next = & (*next)->ai_next;
>  		*next = hold;
> -		hold->ai_next = NULL;
>  		memcpy(&host->addr, hold->ai_addr, hold->ai_addrlen);
>  		addr_set_port(&host->addr, 0);
>  		host->retries = 0;

which I think is wrong, and wondering why:

> @@ -394,7 +408,11 @@ notify_host(int sock, struct nsm_host *host)
>  	}
>  	len = (p - msgbuf) << 2;
>  
> -	sendto(sock, msgbuf, len, 0, (struct sockaddr *) &dest, sizeof(dest));
> +	if (sendto(sock, msgbuf, len, 0, (struct sockaddr *) &dest, sizeof(dest)) < 0)
> +		nsm_log(LOG_WARNING, "Sending Reboot Notification to "
> +			"'%s' failed: errno %d (%s)", host->name, errno, strerror(errno));
> +	
> +	return 0;
>  }
>  
>  /*

Yes, I believe it addresses those comments.

Acked-by: NeilBrown <neilb@suse.de>

Thanks!
NeilBrown

  reply	other threads:[~2008-07-17  2:41 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-15  6:21 [PATCH] sm-notify: perform DNS lookup in the background Neil Brown
     [not found] ` <18556.16890.235207.711721-wvvUuzkyo1EYVZTmpyfIwg@public.gmane.org>
2008-07-15 15:31   ` Chuck Lever
     [not found]     ` <76bd70e30807150831l294c7f0as8ba53709e71d5827-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-07-16 18:43       ` Steve Dickson
2008-07-17  2:41         ` Neil Brown [this message]
     [not found]           ` <18558.45412.19541.657376-wvvUuzkyo1EYVZTmpyfIwg@public.gmane.org>
2008-07-17 10:29             ` Steve Dickson
2008-07-17 22:46               ` Neil Brown
2008-07-17 15:09             ` Chuck Lever
2008-07-17 22:59               ` Neil Brown
     [not found]                 ` <18559.52918.675492.673560-wvvUuzkyo1EYVZTmpyfIwg@public.gmane.org>
2008-07-18  4:41                   ` 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=18558.45412.19541.657376@notabene.brown \
    --to=neilb@suse.de \
    --cc=SteveD@redhat.com \
    --cc=chucklever@gmail.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