From: David Miller <davem@davemloft.net>
To: bhutchings@solarflare.com
Cc: gregkh@linuxfoundation.org, gregory.v.rose@intel.com,
stable@vger.kernel.org, e1000-devel@lists.sourceforge.net,
netdev@vger.kernel.org, linux-net-drivers@solarflare.com
Subject: Re: [PATCH 3.0.y 0/3] rtnetlink: Fix problem with buffer allocation
Date: Thu, 03 Jan 2013 16:36:14 -0800 (PST) [thread overview]
Message-ID: <20130103.163614.162474717714949991.davem@davemloft.net> (raw)
In-Reply-To: <1357259449.2685.60.camel@bwh-desktop.uk.solarflarecom.com>
From: Ben Hutchings <bhutchings@solarflare.com>
Date: Fri, 4 Jan 2013 00:30:49 +0000
> These patches fix the problem that interface information including many
> VFs is too large for the 4K buffers used by glibc and other clients.
> This breaks many network services.
>
> The first of these ('rtnetlink: Compute and store minimum ifinfo dump
> size') went into 3.1 and has also been included in SLE11 SP2. The
> second and third were acked by David Miller and included in 3.2.34.
>
> I've applied and briefly tested these changes in conjunction with a
> backport of the sfc driver to SLE11 SP3.
I'm fine with these going into 3.0.x-stable, thanks for doing the
backport.
next prev parent reply other threads:[~2013-01-04 0:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-04 0:30 [PATCH 3.0.y 0/3] rtnetlink: Fix problem with buffer allocation Ben Hutchings
2013-01-04 0:32 ` [PATCH 3.0.y 1/3] rtnetlink: Compute and store minimum ifinfo dump size Ben Hutchings
2013-01-04 0:33 ` [PATCH 3.0.y 2/3] rtnetlink: Fix problem with buffer allocation Ben Hutchings
2013-01-04 18:39 ` Greg Rose
2013-01-04 0:34 ` [PATCH 3.0.y 3/3] rtnetlink: fix rtnl_calcit() and rtnl_dump_ifinfo() Ben Hutchings
2013-01-04 18:40 ` Greg Rose
2013-01-04 0:36 ` David Miller [this message]
2013-01-14 21:04 ` [PATCH 3.0.y 0/3] rtnetlink: Fix problem with buffer allocation Greg Kroah-Hartman
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=20130103.163614.162474717714949991.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=bhutchings@solarflare.com \
--cc=e1000-devel@lists.sourceforge.net \
--cc=gregkh@linuxfoundation.org \
--cc=gregory.v.rose@intel.com \
--cc=linux-net-drivers@solarflare.com \
--cc=netdev@vger.kernel.org \
--cc=stable@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 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 NNTP newsgroup(s).