netdev - regression when connecting to ipv6 localhost

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAO_aot5U16KLjqtXp2ZS7d+T0WvVY7OXPaA3t2bbN=uvboVV3Q@mail.gmail.com>
Date:	Sun, 14 Oct 2012 17:38:21 +0200
From:	Jan Hinnerk Stosch <janhinnerk.stosch@...il.com>
To:	netdev@...r.kernel.org
Subject: regression when connecting to ipv6 localhost

Hi,
I detected a small regression since linux 3.6.0:
When I run "ntpq -p" to query the status of my ntp-daemon I receive a
timeout (localhost.localdomain: timed out, nothing received
***Request timed out). Strace shows that connecting to the ipv6
loopback interface times out. If I explicitly use ipv4 (ntpq -4 -p)
everything works as intended. Downgrading to linux 3.5.6 solves that
issue.
I reported a bug both to my distribution
(https://bugs.archlinux.org/task/31775) and to the kernel bugtracker
(https://bugzilla.kernel.org/show_bug.cgi?id=48741) not knowing
exactly which component caused the regression, so I was told to ask
this here. At the kernel-report you find an strace and tcpdump output.
If you need any further information just tell me, but be patient as me
kernel knowledge tends to zero.
Thanks in advance, Jan Hinnerk
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html