netdev - Regression: "rtnetlink: Compute and store minimum ifinfo dump size" breaks glibc's getifaddrs()

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: <4F229A5F.4050600@citrix.com>
Date:	Fri, 27 Jan 2012 12:36:47 +0000
From:	David Vrabel <david.vrabel@...rix.com>
To:	"netdev@...r.kernel.org" <netdev@...r.kernel.org>
CC:	Greg Rose <gregory.v.rose@...el.com>,
	"David S. Miller" <davem@...emloft.net>
Subject: Regression: "rtnetlink: Compute and store minimum ifinfo dump size"
 breaks glibc's getifaddrs()

Changeset c7ac8679bec9397afe8918f788cbcef88c38da54 (rtnetlink: Compute
and store minimum ifinfo dump size) applied to 3.1 increased the maximum
size of the RTM_GETLINK message response.

glibc's getifaddrs() function uses a page sized (4 KiB) buffer for the
RTM_GETLINK response and returns a failure if the message is truncated.
This buffer is not large enough if there is a network card with many
virtual functions.

What do you recommend to resolve this regression?

David
--
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