netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Hellstrom <daniel@gaisler.com>
To: davem@davemloft.net
Cc: netdev@vger.kernel.org, kristoffer@gaisler.com
Subject: [PATCH 4/7 v2] GRETH: fixed skb buffer memory leak on frame errors
Date: Fri, 14 Jan 2011 14:02:40 +0100	[thread overview]
Message-ID: <1295010163-2585-4-git-send-email-daniel@gaisler.com> (raw)
In-Reply-To: <1295010163-2585-1-git-send-email-daniel@gaisler.com>

A new SKB buffer should not be allocated when the old SKB is reused.

Signed-off-by: Daniel Hellstrom <daniel@gaisler.com>
---
 drivers/net/greth.c |   18 ++++++++++++++----
 1 files changed, 14 insertions(+), 4 deletions(-)

diff --git a/drivers/net/greth.c b/drivers/net/greth.c
index 869e38d..9386bce 100644
--- a/drivers/net/greth.c
+++ b/drivers/net/greth.c
@@ -870,10 +870,9 @@ static int greth_rx_gbit(struct net_device *dev, int limit)
 			}
 		}
 
-		/* Allocate new skb to replace current */
-		newskb = netdev_alloc_skb(dev, MAX_FRAME_SIZE + NET_IP_ALIGN);
-
-		if (!bad && newskb) {
+		/* Allocate new skb to replace current, not needed if the
+		 * current skb can be reused */
+		if (!bad && (newskb=netdev_alloc_skb(dev, MAX_FRAME_SIZE + NET_IP_ALIGN))) {
 			skb_reserve(newskb, NET_IP_ALIGN);
 
 			dma_addr = dma_map_single(greth->dev,
@@ -910,11 +909,22 @@ static int greth_rx_gbit(struct net_device *dev, int limit)
 				if (net_ratelimit())
 					dev_warn(greth->dev, "Could not create DMA mapping, dropping packet\n");
 				dev_kfree_skb(newskb);
+				/* reusing current skb, so it is a drop */
 				dev->stats.rx_dropped++;
 			}
+		} else if (bad) {
+			/* Bad Frame transfer, the skb is reused */
+			dev->stats.rx_dropped++;
 		} else {
+			/* Failed Allocating a new skb. This is rather stupid
+			 * but the current "filled" skb is reused, as if
+			 * transfer failure. One could argue that RX descriptor
+			 * table handling should be divided into cleaning and
+			 * filling as the TX part of the driver
+			 */
 			if (net_ratelimit())
 				dev_warn(greth->dev, "Could not allocate SKB, dropping packet\n");
+			/* reusing current skb, so it is a drop */
 			dev->stats.rx_dropped++;
 		}
 
-- 
1.5.4


  parent reply	other threads:[~2011-01-14 13:02 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-14 13:02 [PATCH 1/7 v2] GRETH: added raw AMBA vendor/device number to match against Daniel Hellstrom
2011-01-14 13:02 ` [PATCH 2/7 v2] GRETH: fix opening/closing Daniel Hellstrom
2011-01-14 20:46   ` David Miller
2011-01-14 13:02 ` [PATCH 3/7 v2] GRETH: GBit transmit descriptor handling optimization Daniel Hellstrom
2011-01-14 20:46   ` David Miller
2011-01-14 13:02 ` Daniel Hellstrom [this message]
2011-01-14 20:46   ` [PATCH 4/7 v2] GRETH: fixed skb buffer memory leak on frame errors David Miller
2011-01-14 13:02 ` [PATCH 5/7 v2] GRETH: avoid writing bad speed/duplex when setting transfer mode Daniel Hellstrom
2011-01-14 20:46   ` David Miller
2011-01-14 13:02 ` [PATCH 6/7 v2] GRETH: handle frame error interrupts Daniel Hellstrom
2011-01-14 20:46   ` David Miller
2011-01-14 13:02 ` [PATCH 7/7 v2] GRETH: resolve SMP issues and other problems Daniel Hellstrom
2011-01-14 20:47   ` David Miller
2011-01-14 20:46 ` [PATCH 1/7 v2] GRETH: added raw AMBA vendor/device number to match against David Miller

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=1295010163-2585-4-git-send-email-daniel@gaisler.com \
    --to=daniel@gaisler.com \
    --cc=davem@davemloft.net \
    --cc=kristoffer@gaisler.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 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).