All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Howells <dhowells@redhat.com>
To: Bob Liu <lliubbo@gmail.com>
Cc: dhowells@redhat.com, akpm@linux-foundation.org,
	linux-mm@kvack.org, hughd@google.com, viro@zeniv.linux.org.uk,
	hch@lst.de, npiggin@kernel.dk, tj@kernel.org,
	lethal@linux-sh.org, magnus.damm@gmail.com
Subject: Re: [PATCH] ramfs: fix memleak on no-mmu arch
Date: Fri, 01 Apr 2011 16:19:10 +0100	[thread overview]
Message-ID: <7980.1301671150@redhat.com> (raw)
In-Reply-To: <1301290355-8980-1-git-send-email-lliubbo@gmail.com>

Bob Liu <lliubbo@gmail.com> wrote:

> On no-mmu arch, there is a memleak duirng shmem test.
> The cause of this memleak is ramfs_nommu_expand_for_mapping() added page
> refcount to 2 which makes iput() can't free that pages.

Sorry I haven't got around to looking at this yet; it's going to have to wait
till I get back from the US in just over a week.

David

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  parent reply	other threads:[~2011-04-01 15:19 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-28  5:32 [PATCH] ramfs: fix memleak on no-mmu arch Bob Liu
2011-03-29  0:02 ` Andrew Morton
2011-03-29 11:06   ` Bob Liu
2011-04-01  8:25   ` Bob Liu
2011-04-02  3:39     ` Hugh Dickins
2011-04-02  3:35   ` Hugh Dickins
2011-04-01 15:19 ` David Howells [this message]
2011-04-02  2:52 ` Hugh Dickins
  -- strict thread matches above, loose matches on Subject: below --
2011-04-13 16:45 David Howells
2011-04-13 16:45 ` David Howells

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=7980.1301671150@redhat.com \
    --to=dhowells@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=hch@lst.de \
    --cc=hughd@google.com \
    --cc=lethal@linux-sh.org \
    --cc=linux-mm@kvack.org \
    --cc=lliubbo@gmail.com \
    --cc=magnus.damm@gmail.com \
    --cc=npiggin@kernel.dk \
    --cc=tj@kernel.org \
    --cc=viro@zeniv.linux.org.uk \
    /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.