All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Kasai Takanori <kasai.takanori@jp.fujitsu.com>
Cc: xen-devel <xen-devel@lists.xensource.com>
Subject: Re: [PATCH]Fix memory leak for copy-receiver of netfront
Date: Wed, 11 Jun 2008 22:33:02 +0100	[thread overview]
Message-ID: <4850448E.1020603@goop.org> (raw)
In-Reply-To: <37C8CB88D5C4E2kasai.takanori@jp.fujitsu.com>

Kasai Takanori wrote:
> Hi all,
>
> We found the problem of the memory leak when working with copy-
> receiver of netfront.
>
> The source of a problem is that the fragment page is not released with 
> dev_kfree_skb() because the nr_frags variable of skb is set to 0. 
>
> This is the patch to fix memory leak in netfront.
>   

This code doesn't apply to the current 2.6.25 version of netfront.  The 
only similar code I could see is:

                skb = np->rx_skbs[id];
                mfn = gnttab_end_foreign_transfer_ref(ref);
                gnttab_release_grant_reference(&np->gref_rx_head, ref);
                np->grant_rx_ref[id] = GRANT_INVALID_REF;

                if (0 == mfn) {
                        skb_shinfo(skb)->nr_frags = 0;
                        dev_kfree_skb(skb);
                        noxfer++;
                        continue;
                }


Would you mind reviewing the 2.6.25 version of netfront to see if it 
needs a patch?

Thanks,
    J

  reply	other threads:[~2008-06-11 21:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-11  6:03 [PATCH]Fix memory leak for copy-receiver of netfront Kasai Takanori
2008-06-11 21:33 ` Jeremy Fitzhardinge [this message]
2008-06-12  1:39   ` Kasai Takanori

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=4850448E.1020603@goop.org \
    --to=jeremy@goop.org \
    --cc=kasai.takanori@jp.fujitsu.com \
    --cc=xen-devel@lists.xensource.com \
    /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.