linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Miroslav Benes <mbenes@suse.cz>
To: Michal Hocko <mhocko@kernel.org>
Cc: Maninder Singh <maninder1.s@samsung.com>,
	jeyu@redhat.com, rusty@rustcorp.com.au,
	akpm@linux-foundation.org, chris@chris-wilson.co.uk,
	aryabinin@virtuozzo.com, joonas.lahtinen@linux.intel.com,
	keescook@chromium.org, pavel@ucw.cz, jinb.park7@gmail.com,
	anisse@astier.eu, rafael.j.wysocki@intel.com, zijun_hu@htc.com,
	mingo@kernel.org, mawilcox@microsoft.com, thgarnie@google.com,
	joelaf@google.com, kirill.shutemov@linux.intel.com,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org,
	pankaj.m@samsung.com, ajeet.y@samsung.com,
	hakbong5.lee@samsung.com, a.sahrawat@samsung.com,
	lalit.mohan@samsung.com, cpgs@samsung.com,
	Vaneet Narang <v.narang@samsung.com>
Subject: Re: [PATCH v2] module: check if memory leak by module.
Date: Wed, 29 Mar 2017 10:02:24 +0200 (CEST)	[thread overview]
Message-ID: <alpine.LSU.2.20.1703290958390.4250@pobox.suse.cz> (raw)
In-Reply-To: <20170329074522.GB27994@dhcp22.suse.cz>

On Wed, 29 Mar 2017, Michal Hocko wrote:

> On Wed 29-03-17 11:32:02, Maninder Singh wrote:
> > This patch checks if any module which is going to be unloaded
> > is doing vmalloc memory leak or not.
> 
> Hmm, how can you track _all_ vmalloc allocations done on behalf of the
> module? It is quite some time since I've checked kernel/module.c but
> from my vague understading your check is basically only about statically
> vmalloced areas by module loader. Is that correct? If yes then is this
> actually useful? Were there any bugs in the loader code recently? What
> led you to prepare this patch? All this should be part of the changelog!

Moreover, I don't understand one thing:
  
> > Logs:-
> > [  129.336368] Module [test_module] is getting unloaded before doing vfree

ok, but...

> > +static void check_memory_leak(struct module *mod)
> > +{
> > +	struct vmap_area *va;
> > +
> > +	rcu_read_lock();
> > +	list_for_each_entry_rcu(va, &vmap_area_list, list) {
> > +		if (!(va->flags & VM_VM_AREA))
> > +			continue;
> > +		if ((mod->core_layout.base < va->vm->caller) &&
> > +			(mod->core_layout.base + mod->core_layout.size) > va->vm->caller) {
> > +			pr_err("Module [%s] is getting unloaded before doing vfree\n", mod->name);
> > +			pr_err("Memory still allocated: addr:0x%lx - 0x%lx, pages %u\n",
> > +				va->va_start, va->va_end, va->vm->nr_pages);
> > +			pr_err("Allocating function %pS\n", va->vm->caller);
> > +		}
> > +
> > +	}
> > +	rcu_read_unlock();
> > +}
> > +
> >  /* Free a module, remove from lists, etc. */
> >  static void free_module(struct module *mod)
> >  {
> > +	check_memory_leak(mod);
> > +

Of course, vfree() has not been called yet. It is the beginning of 
free_module(). vfree() is one of the last things you need to do. See 
module_memfree(). If I am not missing something, you get pr_err() 
everytime a module is unloaded.

Regards,
Miroslav

--
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/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2017-03-29  8:02 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20170329060315epcas5p1c6f7ce3aca1b2770c5e1d9aaeb1a27e1@epcas5p1.samsung.com>
2017-03-29  6:02 ` Maninder Singh
2017-03-29  7:45   ` Michal Hocko
2017-03-29  8:02     ` Miroslav Benes [this message]
     [not found]     ` <CGME20170329060315epcas5p1c6f7ce3aca1b2770c5e1d9aaeb1a27e1@epcms5p1>
2017-03-29  9:23       ` Vaneet Narang
2017-03-29 10:43         ` Michal Hocko
2017-03-31  6:49           ` Joel Fernandes
2017-03-31  8:00             ` Michal Hocko
2017-03-31 17:05               ` Joel Fernandes
2017-04-03  7:24                 ` Michal Hocko
2017-03-31 22:18         ` Jessica Yu
2017-03-29 11:05   ` Andrey Ryabinin
2017-03-30 13:37     ` Pavel Machek
2017-03-30 14:31       ` Andrey Ryabinin

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.20.1703290958390.4250@pobox.suse.cz \
    --to=mbenes@suse.cz \
    --cc=a.sahrawat@samsung.com \
    --cc=ajeet.y@samsung.com \
    --cc=akpm@linux-foundation.org \
    --cc=anisse@astier.eu \
    --cc=aryabinin@virtuozzo.com \
    --cc=chris@chris-wilson.co.uk \
    --cc=cpgs@samsung.com \
    --cc=hakbong5.lee@samsung.com \
    --cc=jeyu@redhat.com \
    --cc=jinb.park7@gmail.com \
    --cc=joelaf@google.com \
    --cc=joonas.lahtinen@linux.intel.com \
    --cc=keescook@chromium.org \
    --cc=kirill.shutemov@linux.intel.com \
    --cc=lalit.mohan@samsung.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=maninder1.s@samsung.com \
    --cc=mawilcox@microsoft.com \
    --cc=mhocko@kernel.org \
    --cc=mingo@kernel.org \
    --cc=pankaj.m@samsung.com \
    --cc=pavel@ucw.cz \
    --cc=rafael.j.wysocki@intel.com \
    --cc=rusty@rustcorp.com.au \
    --cc=thgarnie@google.com \
    --cc=v.narang@samsung.com \
    --cc=zijun_hu@htc.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