All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Kent <raven@themaw.net>
To: christof.koehler@bccms.uni-bremen.de
Cc: autofs@vger.kernel.org
Subject: Re: autofs reverts to IPv4 for multi-homed IPv6 server ?
Date: Tue, 26 Apr 2016 17:53:53 +0800	[thread overview]
Message-ID: <1461664433.3218.42.camel@themaw.net> (raw)
In-Reply-To: <1461632818.3218.29.camel@themaw.net>

On Tue, 2016-04-26 at 09:06 +0800, Ian Kent wrote:
> > So re-building and testing autofs on 16.04 with IPv6 could still be
> > useful assuming the segfault is a separable problem (which might not
> > be
> > the case of course) ?
> 
> That most likely will function ok from what I saw.
> 
> Even more surprising is the proximity and availability probe code uses
> the same client creation as the code that has the problem and it seems
> to work ....
> 
> Anyway I can cleanup what I have and send over what's needed to build
> the debs when your ready.
> 
> > 
> > 
> > I can also offer to try to do it with debian testing in a vm. If it
> > also
> > segfaults I could file a bug report hoping to get the maintainer
> > interested, especially if there are no problems with fedora. Shall I
> > try
> > that ? Instead or in addition to the test with IPv6 mentioned above
> > ?
> 
> Not sure how to go about this.
> I think a couple of changes are needed but fiddling with LDFLAGS
> presence and position as I did might not be in line with what the
> Debian
> folks want.
> 
> I suggest we just go along and see what we come up with.

I spent a little more time on this.

I used a smallish sledge hammer approach, building an updated libtirpc
and building dependencies I'm aware of against it, nfs-common and
rpcbind as well as autofs 5.1.1.

I just went straight to libtirpc 1.0.1.

The resulting autofs package didn't show the problem I saw with the
internal hosts map.

So I'd have to say this looks like a library version problem after all.

It seems to me that spending some time to work out how to provide a
lanchpad ppa is probably the best way to get you to a position to test
the IPv6 functionality.

That also means that in time there could be a 14.04 build too, not sure
about that though.

I can't spend more time on this for a little while so I'll need some
time to work out how to do the ppa thing, if in fact I can.

I guess the other thing to worry about is if doing this will annoy the
official downstream maintainer ... maybe we should attempt to make
contact some time.

Ian
--
To unsubscribe from this list: send the line "unsubscribe autofs" in

  reply	other threads:[~2016-04-26  9:53 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-07 14:19 autofs reverts to IPv4 for multi-homed IPv6 server ? Christof Koehler
2016-04-08  4:46 ` Ian Kent
2016-04-08 10:10   ` Ian Kent
2016-04-08 10:14     ` Ian Kent
2016-04-08 12:25     ` Christof Koehler
2016-04-08 14:29       ` Christof Koehler
2016-04-08 15:32         ` Christof Koehler
2016-04-10  2:09           ` Ian Kent
2016-04-08 16:12         ` Christof Koehler
2016-04-08 16:15           ` Christof Koehler
2016-04-10  2:17             ` Ian Kent
2016-04-10  2:14           ` Ian Kent
2016-04-09  1:42         ` Ian Kent
2016-04-09  9:56           ` Christof Koehler
2016-04-10  2:29             ` Ian Kent
2016-04-25  4:40             ` Ian Kent
2016-04-25 15:06               ` Christof Koehler
2016-04-26  1:06                 ` Ian Kent
2016-04-26  9:53                   ` Ian Kent [this message]
2016-04-26 15:27                     ` Christof Koehler
2016-04-27  1:54                       ` Ian Kent
2016-04-27  2:27                         ` Ian Kent
2016-04-27 16:52                         ` Christof Koehler
2016-04-28  2:56                           ` Ian Kent
2016-04-28  3:21                             ` Ian Kent
2016-04-28  9:12                               ` Christof Koehler
2016-04-28  9:10                             ` Christof Koehler
2016-04-28 10:50                               ` Ian Kent
2016-04-28 11:26                                 ` Christof Koehler
2016-04-28 12:40                                   ` Christof Koehler
2016-04-29  1:54                                   ` Ian Kent
2016-04-29 14:10                                     ` Christof Koehler
2016-04-29 14:42                                       ` Christof Koehler
2016-04-30  3:21                                       ` Ian Kent
2016-04-30 11:36                                         ` Christof Koehler
2016-04-30 15:15                                           ` Christof Koehler
2016-04-30 15:16                                           ` Christof Koehler
2016-05-02  6:01                                           ` Ian Kent
2016-05-02 16:08                                             ` Christof Koehler
2016-05-03  7:58                                               ` Ian Kent
2016-05-03 15:13                                                 ` Christof Koehler
2016-05-04  7:20                                                   ` Ian Kent
2016-05-04 12:38                                                     ` Christof Koehler
2016-04-09  1:35       ` Ian Kent
2016-04-11  2:42     ` Ian Kent
2016-04-11 16:32       ` Christof Koehler
2016-04-11 16:35         ` Christof Koehler
2016-04-12  1:07           ` Ian Kent
2016-04-08 11:47   ` Christof Koehler

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=1461664433.3218.42.camel@themaw.net \
    --to=raven@themaw.net \
    --cc=autofs@vger.kernel.org \
    --cc=christof.koehler@bccms.uni-bremen.de \
    /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.