All of lore.kernel.org
 help / color / mirror / Atom feed
From: Markus Pietrek <eu.ml.linux-kernel@digi.com>
To: linux-kernel@vger.kernel.org
Subject: [PATCH] i802.11: fixed memory leak on multicasts
Date: Tue, 24 Apr 2007 09:38:09 +0200	[thread overview]
Message-ID: <462DB3E1.4040504@digi.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 442 bytes --]

Hi,

socket buffers were not always freed when receiving multicasts

Bye,
-- 
Markus Pietrek
Lead Software Engineer
Phone: +49-7667-908-501, Fax: +49-7667-908-200
mailto:markus.pietrek@digi.com

FS Forth-Systeme GmbH
"A Digi International Company"
Kueferstr. 8, 79206 Breisach, Germany
Tax: 07008/12000 / VAT: DE142208834 / Reg. Amtsgericht Freiburg HRB 290212
Directors: Klaus Flesch, Subramanian Krishnan, Dieter Vesper
http://www.digi.com

[-- Attachment #2: patch_memleak_80211.txt --]
[-- Type: text/plain, Size: 790 bytes --]

Index: net/ieee80211/ieee80211_rx.c
===================================================================
RCS file: /data/vcs/cvs/fsforth_products/LxNETES/linux/net/ieee80211/ieee80211_rx.c,v
retrieving revision 1.5
retrieving revision 1.6
diff -c -r1.5 -r1.6
*** net/ieee80211/ieee80211_rx.c	13 Apr 2007 12:39:38 -0000	1.5
--- net/ieee80211/ieee80211_rx.c	23 Apr 2007 15:51:28 -0000	1.6
***************
*** 860,868 ****
  		break;
  	}
  
! 	if (is_packet_for_us)
  		if (!ieee80211_rx(ieee, skb, stats))
  			dev_kfree_skb_irq(skb);
  	return;
  
  drop_free:
--- 860,871 ----
  		break;
  	}
  
! 	if (is_packet_for_us) {
  		if (!ieee80211_rx(ieee, skb, stats))
  			dev_kfree_skb_irq(skb);
+         } else
+                 dev_kfree_skb_irq(skb);
+         
  	return;
  
  drop_free:

                 reply	other threads:[~2007-04-24  7:35 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=462DB3E1.4040504@digi.com \
    --to=eu.ml.linux-kernel@digi.com \
    --cc=linux-kernel@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.