From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Ben Hutchings <bhutchings@solarflare.com>
Cc: David Miller <davem@davemloft.net>,
Greg Rose <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: Mon, 14 Jan 2013 13:04:40 -0800 [thread overview]
Message-ID: <20130114210440.GB24751@kroah.com> (raw)
In-Reply-To: <1357259449.2685.60.camel@bwh-desktop.uk.solarflarecom.com>
On Fri, Jan 04, 2013 at 12:30:49AM +0000, Ben Hutchings wrote:
> 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.
All now applied, thanks.
greg k-h
prev parent reply other threads:[~2013-01-14 21:04 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 ` [PATCH 3.0.y 0/3] rtnetlink: Fix problem with buffer allocation David Miller
2013-01-14 21:04 ` Greg Kroah-Hartman [this message]
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=20130114210440.GB24751@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=bhutchings@solarflare.com \
--cc=davem@davemloft.net \
--cc=e1000-devel@lists.sourceforge.net \
--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 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.