From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
To: Hagen Paul Pfeifer <hagen@jauu.net>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [PATCH net-next] ixgb: relax stack usage of 768 Byte
Date: Fri, 16 Sep 2011 16:08:40 -0700 [thread overview]
Message-ID: <1316214520.3661.87.camel@jtkirshe-mobl> (raw)
In-Reply-To: <1316208897-4557-1-git-send-email-hagen@jauu.net>
[-- Attachment #1: Type: text/plain, Size: 508 bytes --]
On Fri, 2011-09-16 at 14:34 -0700, Hagen Paul Pfeifer wrote:
> ixgb_set_multi() will push (128 * 6) byte on the stack to set the
> multicast filter. Fix this by allocate the scratch buffer on the heap.
>
> Signed-off-by: Hagen Paul Pfeifer <hagen@jauu.net>
> Cc: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
> ---
> drivers/net/ethernet/intel/ixgb/ixgb_main.c | 8 ++++++--
> 1 files changed, 6 insertions(+), 2 deletions(-)
Thanks Hagen! I have added the patch to my queue of ixgbe patches.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 490 bytes --]
prev parent reply other threads:[~2011-09-16 23:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-16 21:34 [PATCH net-next] ixgb: relax stack usage of 768 Byte Hagen Paul Pfeifer
2011-09-16 23:08 ` Jeff Kirsher [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=1316214520.3661.87.camel@jtkirshe-mobl \
--to=jeffrey.t.kirsher@intel.com \
--cc=hagen@jauu.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox