From: Daniel Alvarez <dalvarez@redhat.com>
To: libc-alpha@sourceware.org
Cc: Daniel Alvarez <dalvarez@redhat.com>
Subject: [PATCH] [BZ #21812] getifaddrs() Don't return ifa entries with NULL names
Date: Mon, 24 Jul 2017 20:58:00 -0000 [thread overview]
Message-ID: <20170724205618.21515-1-dalvarez@redhat.com> (raw)
Due to bug 21812, a lookup operation in map_newlink() turns out
into an insert because of holes in the interface part of the map.
This leads to incorrectly set the name of the interface to NULL when
the interface is not present for the address being processed (most
likely because the interface was added between the RTM_GETLINK and
RTM_GETADDR calls to the kernel).
This patch checks this condition and retries the whole operation.
Hopes are that next time the interface corresponding to the address
entry is present in the list and correct name is returned.
Signed-off-by: Daniel Alvarez <dalvarez@redhat.com>
---
sysdeps/unix/sysv/linux/ifaddrs.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/sysdeps/unix/sysv/linux/ifaddrs.c b/sysdeps/unix/sysv/linux/ifaddrs.c
index 3bc9902..62421e8 100644
--- a/sysdeps/unix/sysv/linux/ifaddrs.c
+++ b/sysdeps/unix/sysv/linux/ifaddrs.c
@@ -740,7 +740,7 @@ getifaddrs_internal (struct ifaddrs **ifap)
{
int idx = map_newlink (ifam->ifa_index - 1, ifas,
map_newlink_data, newlink);
- if (__glibc_unlikely (idx == -1))
+ if (__glibc_unlikely (idx == -1) || ifas[idx].ifa.ifa_name == NULL)
goto try_again;
ifas[ifa_index].ifa.ifa_name = ifas[idx].ifa.ifa_name;
}
--
2.9.3
next reply other threads:[~2017-07-24 20:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-24 20:58 Daniel Alvarez [this message]
2017-08-29 10:37 ` Florian Weimer
2018-06-15 13:29 Daniel Alvarez
2018-06-15 19:12 ` Adhemerval Zanella
2018-06-29 6:58 ` Daniel Alvarez Sanchez
2018-06-29 9:38 ` Florian Weimer
2018-06-29 8:22 ` Florian Weimer
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=20170724205618.21515-1-dalvarez@redhat.com \
--to=dalvarez@redhat.com \
--cc=libc-alpha@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).