From: Florian Weimer <fweimer@redhat.com>
To: Hannes Frederic Sowa <hannes@stressinduktion.org>,
GNU C Library <libc-alpha@sourceware.org>,
davem@davemloft.net
Cc: Hannes Sowa <hannes@redhat.com>, netdev@vger.kernel.org
Subject: Re: [PATCH] glibc: Terminate process on invalid netlink response from kernel [BZ #12926]
Date: Tue, 3 Nov 2015 15:00:03 +0100 [thread overview]
Message-ID: <5638BDE3.2040608@redhat.com> (raw)
In-Reply-To: <1446558492.1880442.427793993.78B20B4F@webmail.messagingengine.com>
On 11/03/2015 02:48 PM, Hannes Frederic Sowa wrote:
> Hello,
>
> On Fri, Oct 23, 2015, at 21:07, Florian Weimer wrote:
>> (By the way, we'd also love to have a better kernel interface to fulfill
>> the needs for getaddrinfo address sorting. The netlink requests we
>> currently use are much too slow if the host has many addresses
>> configured.)
>
> One solution would be to finish the IPv6 ioctl interface to list
> addresses. The ioctl interface would need less memory allocations and is
> a synchronous interface which would make it much more easier for glibc
> to deal with. No timeouts and retries like with netlink are necessary.
The more fundamental question is whether we actually have to copy all
the addresses to userspace. In the end, it may be better to hand a list
of destination addresses to the kernel and have it sort them according
to some algorithm. But for the algorithm proposed in RFC 6724 section
6, this may be not worth the effort because there are so many
configurable bits.
I still think most of the address sorting is bogus because it appears to
make guarantees which can break after renumbering.
Florian
next prev parent reply other threads:[~2015-11-03 14:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-23 20:07 [PATCH] glibc: Terminate process on invalid netlink response from kernel [BZ #12926] Florian Weimer
2015-10-24 4:22 ` Mike Frysinger
2015-11-03 13:40 ` [PATCH v2] " Florian Weimer
2015-11-03 13:48 ` [PATCH] " Hannes Frederic Sowa
2015-11-03 14:00 ` Florian Weimer [this message]
2015-11-05 14:36 ` Hannes Frederic Sowa
2015-11-03 16:20 ` David Miller
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=5638BDE3.2040608@redhat.com \
--to=fweimer@redhat.com \
--cc=davem@davemloft.net \
--cc=hannes@redhat.com \
--cc=hannes@stressinduktion.org \
--cc=libc-alpha@sourceware.org \
--cc=netdev@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).