linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: wang.bo116@zte.com.cn
To: richard -rw- weinberger <richard.weinberger@gmail.com>
Cc: artem.bityutskiy@linux.intel.com, cui.yunfeng@zte.com.cn,
	LKML <linux-kernel@vger.kernel.org>,
	"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
	liu.dong3@zte.com.cn
Subject: RE: Re: [PATCH] UBI: fix memory leak when use fastmap
Date: Thu, 2 May 2013 16:30:01 +0800	[thread overview]
Message-ID: <OF2D2AAAE7.DA66471C-ON48257B5F.002C2C42-48257B5F.002EB4C8@zte.com.cn> (raw)

> Hi!
> 
> On Tue, Apr 16, 2013 at 10:53 AM,  <wang.bo116@zte.com.cn> wrote:
> > Hello,
> >         Sorry, there is still something wrong with the previous 
patch's
> > format, try to submit it again. When use ubi fastmap, there is a 
memory
> > leak which will make destroy_ai() fail to free the slab alloced in
> > scan_fast(). The following patch fix this problem by use a temporary
> > "ubi_attach_info" variable in scan_fast().
> 
> Thanks a lot for your patch!
> 
> Did you test it well?
> We need to make sure that it does the right thing for the following 
cases:
> 1. fastmap disabled, attaching a non-fastmap volume
> 1. fastmap disabled, attaching a fastmap volume
> 3. fastmap enabled, attaching a non-fastmap volume
> 4. fastmap enablled, attaching a fastmap volume
> 
> --
> Thanks,
> //richard


Thanks for your advice. I consider this problem like this:
1: if fastmap not config, ubi_attach() just call scan_all(ubi, ai, 0), 
there is nothing changed, so there is all right.

2: if fastmap config, and force_scan is 0, ubi_attach() will call 
scan_fast(), when scan_fast() return, temp ai used in scan_fast() has been 
free, and there will be two conditions:
A: scan_fast() return UBI_NO_FASTMAP(may be flash is empty or attaching a 
non-fastmap volume), all ubi_attach() need is to call scan_all(ubi, ai, 0) 
to scan all blocks. 
B: scan_fast() return UBI_BAD_FASTMAP, ubi_attach() first free ai used in 
ubi_scan_fastmap(), then alloc a clean ai, at last call scan_all(ubi, ai, 
0) to scan all blocks.

3: if fastmap config, and force_scan is 1, just call scan_all(ubi, ai, 0).

This patch pass the following cases(include attach and detach):
1. fastmap config, flash is empty,fm_autoconvert is 1.
2. fastmap config, flash is empty,fm_autoconvert is 0.
3. fastmap config, attaching a fastmap volume
4. fastmap config, attaching a bad fastmap volume
5. fastmap config, attaching a non-fastmap volume
6. fastmap not config, attaching a fastmap volume
7. fastmap not config, attaching a non-fastmap volume
8. fastmap not config, flash is empty.

By the way, the problem may cause ubi_attach() fail after ubi detach when 
CONFIG_DEBUG_VM config. 
The reason is that ubi_attach() will alloc a slab cache, but the 
kmem_cache_sanity_check() will find the slab cache is already exist(not 
been free after last detach), so slab cache alloc fail, and ubi_attach() 
fail, too.

Thanks 
--wangbo

             reply	other threads:[~2013-05-02  9:20 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-02  8:30 wang.bo116 [this message]
2013-05-02 19:21 ` Re: [PATCH] UBI: fix memory leak when use fastmap richard -rw- weinberger
2013-05-03  3:31   ` wang.bo116
2013-05-13  8:08     ` richard -rw- weinberger
2013-05-23 12:00       ` wang.bo116
2013-05-23 12:13         ` richard -rw- weinberger
2013-05-27  8:02           ` [PATCH] UBI: Fastmap: Fix memory leak Thomas Weber
2013-05-27  8:10             ` Richard Weinberger
2013-05-27  8:22               ` Thomas Weber
2013-05-29 12:27               ` Artem Bityutskiy
2013-05-29 12:28                 ` Richard Weinberger

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=OF2D2AAAE7.DA66471C-ON48257B5F.002C2C42-48257B5F.002EB4C8@zte.com.cn \
    --to=wang.bo116@zte.com.cn \
    --cc=artem.bityutskiy@linux.intel.com \
    --cc=cui.yunfeng@zte.com.cn \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=liu.dong3@zte.com.cn \
    --cc=richard.weinberger@gmail.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 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).