aboutsummaryrefslogtreecommitdiff
path: root/nscd
diff options
context:
space:
mode:
authorFabian Vogt <fvogt@suse.de>2022-07-27 11:44:07 +0200
committerMartin Liska <mliska@suse.cz>2022-08-29 21:54:20 +0200
commit02ca25fef2785974011e9c5beecc99b900b69fd7 (patch)
tree251eb615a367ad982b036ab803035cc24e0dbba6 /nscd
parentca6466e8be32369a658035d69542d47603e58a99 (diff)
downloadglibc-02ca25fef2785974011e9c5beecc99b900b69fd7.zip
glibc-02ca25fef2785974011e9c5beecc99b900b69fd7.tar.gz
glibc-02ca25fef2785974011e9c5beecc99b900b69fd7.tar.bz2
nscd: Fix netlink cache invalidation if epoll is used [BZ #29415]
Processes cache network interface information such as whether IPv4 or IPv6 are enabled. This is only checked again if the "netlink timestamp" provided by nscd changed, which is triggered by netlink socket activity. However, in the epoll handler for the netlink socket, it was missed to assign the new timestamp to the nscd database. The handler for plain poll did that properly, copy that over. This bug caused that e.g. processes which started before network configuration got unusuable addresses from getaddrinfo, like IPv6 only even though only IPv4 is available: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/1041 It's a bit hard to reproduce, so I verified this by checking the timestamp on calls to __check_pf manually. Without this patch it's stuck at 1, now it's increasing on network changes as expected. Signed-off-by: Fabian Vogt <fvogt@suse.de>
Diffstat (limited to 'nscd')
-rw-r--r--nscd/connections.c3
1 files changed, 2 insertions, 1 deletions
diff --git a/nscd/connections.c b/nscd/connections.c
index 61d1674..531d2e8 100644
--- a/nscd/connections.c
+++ b/nscd/connections.c
@@ -2284,7 +2284,8 @@ main_loop_epoll (int efd)
sizeof (buf))) != -1)
;
- __bump_nl_timestamp ();
+ dbs[hstdb].head->extra_data[NSCD_HST_IDX_CONF_TIMESTAMP]
+ = __bump_nl_timestamp ();
}
# endif
else