linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Hugh Dickins <hughd@google.com>
To: Bob Liu <lliubbo@gmail.com>
Cc: 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, dhowells@redhat.com, lethal@linux-sh.org,
	magnus.damm@gmail.com
Subject: Re: [PATCH] ramfs: fix memleak on no-mmu arch
Date: Fri, 1 Apr 2011 19:52:37 -0700 (PDT)	[thread overview]
Message-ID: <alpine.LSU.2.00.1104011929090.3340@sister.anvils> (raw)
In-Reply-To: <1301290355-8980-1-git-send-email-lliubbo@gmail.com>

On Mon, 28 Mar 2011, Bob Liu 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.
> 
> The simple test file is like this:
> int main(void)
> {
> 	int i;
> 	key_t k = ftok("/etc", 42);
> 
> 	for ( i=0; i<100; ++i) {
> 		int id = shmget(k, 10000, 0644|IPC_CREAT);
> 		if (id == -1) {
> 			printf("shmget error\n");
> 		}
> 		if(shmctl(id, IPC_RMID, NULL ) == -1) {
> 			printf("shm  rm error\n");
> 			return -1;
> 		}
> 	}
> 	printf("run ok...\n");
> 	return 0;
> }
> 
> And the result:
> root:/> free
>              total         used         free       shared      buffers
> Mem:         60320        16644        43676            0            0
> -/+ buffers:              16644        43676
> root:/> shmem
> run ok...
> root:/> free
>              total         used         free       shared      buffers
> Mem:         60320        17912        42408            0            0
> -/+ buffers:              17912        42408
> root:/> shmem
> run ok...
> root:/> free
>              total         used         free       shared      buffers
> Mem:         60320        19096        41224            0            0
> -/+ buffers:              19096        41224
> root:/> shmem
> run ok...
> root:/> free
>              total         used         free       shared      buffers
> Mem:         60320        20296        40024            0            0
> -/+ buffers:              20296        40024
> root:/> shmem
> run ok...
> root:/> free
>              total         used         free       shared      buffers
> Mem:         60320        21496        38824            0            0
> -/+ buffers:              21496        38824
> root:/> shmem 
> run ok...
> root:/> free
>              total         used         free       shared      buffers
> Mem:         60320        22692        37628            0            0
> -/+ buffers:              22692        37628
> root:/> 
> 
> After this patch the test result is:(no memleak anymore)
> root:/> 
> root:/> free
>              total         used         free       shared      buffers
> Mem:         60320        16580        43740            0            0
> -/+ buffers:              16580        43740
> root:/> shmem
> run ok...
> root:/> free
>              total         used         free       shared      buffers
> Mem:         60320        16668        43652            0            0
> -/+ buffers:              16668        43652
> root:/> shmem
> run ok...
> root:/> free
>              total         used         free       shared      buffers
> Mem:         60320        16668        43652            0            0
> -/+ buffers:              16668        43652
> root:/> shmem
> run ok...
> root:/> free
>              total         used         free       shared      buffers
> Mem:         60320        16668        43652            0            0
> -/+ buffers:              16668        43652
> root:/> shmem
> run ok...
> root:/> free
>              total         used         free       shared      buffers
> Mem:         60320        16668        43652            0            0
> -/+ buffers:              16668        43652
> root:/> shmem
> run ok...
> root:/> free
>              total         used         free       shared      buffers
> Mem:         60320        16668        43652            0            0
> -/+ buffers:              16668        43652
> root:/> 
> 
> Signed-off-by: Bob Liu <lliubbo@gmail.com>

Acked-by: Hugh Dickins <hughd@google.com>
Cc: stable@kernel.org

Sorry for being so slow to get back to this, Bob.

And I'm sorry that in my original patch for it, I just couldn't
resist a little tidying up while I was there: which led Paul to
observe correctly that the function would be better off using
alloc_pages_exact(); which made me pause before responding,
seeing a proposal to rename that to get_free_pages_exact().

Aaaaaah, let's go with your patch below, which fixes the bug in
the simplest fashion; and do any tidying up at leisure later on.

I see Andrew is questioning the correctness of this patch:
let me answer his mail separately.

Hugh

> ---
>  fs/ramfs/file-nommu.c |    1 +
>  1 files changed, 1 insertions(+), 0 deletions(-)
> 
> diff --git a/fs/ramfs/file-nommu.c b/fs/ramfs/file-nommu.c
> index 9eead2c..fbb0b47 100644
> --- a/fs/ramfs/file-nommu.c
> +++ b/fs/ramfs/file-nommu.c
> @@ -112,6 +112,7 @@ int ramfs_nommu_expand_for_mapping(struct inode *inode, size_t newsize)
>  		SetPageDirty(page);
>  
>  		unlock_page(page);
> +		put_page(page);
>  	}
>  
>  	return 0;
> -- 
> 1.6.3.3

--
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-02  2:52 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-28  5:32 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
2011-04-02  2:52 ` Hugh Dickins [this message]
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=alpine.LSU.2.00.1104011929090.3340@sister.anvils \
    --to=hughd@google.com \
    --cc=akpm@linux-foundation.org \
    --cc=dhowells@redhat.com \
    --cc=hch@lst.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox