From: David Miller <davem@davemloft.net>
To: paul@pmarks.net
Cc: netdev@vger.kernel.org
Subject: Re: When should kfree_skb be used?
Date: Thu, 08 May 2008 23:41:22 -0700 (PDT) [thread overview]
Message-ID: <20080508.234122.20422788.davem@davemloft.net> (raw)
In-Reply-To: <8e5b27790805082334g6c5a1752pd42ab291ac6b33af@mail.gmail.com>
From: "Paul Marks" <paul@pmarks.net>
Date: Thu, 8 May 2008 23:34:59 -0700
> I've been looking at more uses of pskb_may_pull(), and almost all of
> them seem to kfree_skb() after a failure. Could this occurence in
> sit.c be a bug? It looks like this line was added by davem for linux
> 2.4.4 in 2001, and hasn't changed since.
Yep, looks like a leak. The following should fix it, thanks
for the report:
>From 36ca34cc3b8335eb1fe8bd9a1d0a2592980c3f02 Mon Sep 17 00:00:00 2001
From: David S. Miller <davem@davemloft.net>
Date: Thu, 8 May 2008 23:40:26 -0700
Subject: [PATCH] sit: Add missing kfree_skb() on pskb_may_pull() failure.
Noticed by Paul Marks <paul@pmarks.net>.
Signed-off-by: David S. Miller <davem@davemloft.net>
---
net/ipv6/sit.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/net/ipv6/sit.c b/net/ipv6/sit.c
index 4b2f103..5a6fab9 100644
--- a/net/ipv6/sit.c
+++ b/net/ipv6/sit.c
@@ -596,9 +596,9 @@ static int ipip6_rcv(struct sk_buff *skb)
}
icmp_send(skb, ICMP_DEST_UNREACH, ICMP_PORT_UNREACH, 0);
- kfree_skb(skb);
read_unlock(&ipip6_lock);
out:
+ kfree_skb(skb);
return 0;
}
--
1.5.5.1.57.g5909c
next prev parent reply other threads:[~2008-05-09 6:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-09 4:49 When should kfree_skb be used? Paul Marks
2008-05-09 6:34 ` Paul Marks
2008-05-09 6:41 ` David Miller [this message]
2008-05-09 6:55 ` Paul Marks
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=20080508.234122.20422788.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=paul@pmarks.net \
/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).