From: David Vrabel <david.vrabel@citrix.com>
To: "netdev@vger.kernel.org" <netdev@vger.kernel.org>
Cc: Greg Rose <gregory.v.rose@intel.com>,
"David S. Miller" <davem@davemloft.net>
Subject: Regression: "rtnetlink: Compute and store minimum ifinfo dump size" breaks glibc's getifaddrs()
Date: Fri, 27 Jan 2012 12:36:47 +0000 [thread overview]
Message-ID: <4F229A5F.4050600@citrix.com> (raw)
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
next reply other threads:[~2012-01-27 12:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-27 12:36 David Vrabel [this message]
2012-01-27 21:53 ` Regression: "rtnetlink: Compute and store minimum ifinfo dump size" breaks glibc's getifaddrs() David Miller
2012-01-27 22:26 ` Štefan Gula
2012-01-30 16:50 ` Rose, Gregory V
2012-01-30 16:58 ` David Miller
2012-01-30 17:02 ` Rose, Gregory V
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=4F229A5F.4050600@citrix.com \
--to=david.vrabel@citrix.com \
--cc=davem@davemloft.net \
--cc=gregory.v.rose@intel.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.