From: Markus Metzger <markus.t.metzger@googlemail.com>
To: Frederic Weisbecker <fweisbec@gmail.com>
Cc: Rakib Mullick <rakib.mullick@gmail.com>,
Ingo Molnar <mingo@elte.hu>,
Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
markus.t.metzger@gmail.com
Subject: Re: [PATCH -mm] tracing: Fix section mismatch in trace_hw_branches.c
Date: Mon, 23 Feb 2009 11:21:04 +0100 [thread overview]
Message-ID: <a430082a0902230221p4f128073id93b5d5d4184ddf1@mail.gmail.com> (raw)
In-Reply-To: <20090222162234.GA6003@nowhere>
On Sun, Feb 22, 2009 at 5:22 PM, Frederic Weisbecker <fweisbec@gmail.com> wrote:
> On Sun, Feb 22, 2009 at 07:33:08PM +0600, Rakib Mullick wrote:
>> On 2/21/09, Frederic Weisbecker <fweisbec@gmail.com> wrote:
>> > So, unless I missed something, this patch seems to me very dangerous.
>> > The init and reset callbacks of a tracer can be called at any time, not only
>> > on initcalls time (__init functions are freed from memory after the middle stage
>> > of the boot).
>> > With this patch, on UP we will dereference freed memory while activating this tracer.
>> If the init and reset callbacks of a tracer can be called regardless
>> of cpu hotpluging then it is. If the tracer's init or reset doesn't
>> rely on cpuhotplug then it shouldn't use it.
>> There's a another way to fix the warning is by remove __cpuinitdata
>> from bts_hotcpu_notifier.
[...]
> But removing __cpuinitdata will mean a kind of waste of memory (though it's only
> a little struct).
Plus the hotplug handler function. It's still not much.
I'll send out a patch following Frederic's suggestion to register the
hotplug notifier once in init.
thanks and regards,
markus.
next prev parent reply other threads:[~2009-02-23 10:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-14 3:36 Rakib Mullick
2009-02-15 19:41 ` Ingo Molnar
2009-02-21 15:22 ` Frederic Weisbecker
2009-02-22 13:33 ` Rakib Mullick
2009-02-22 16:22 ` Frederic Weisbecker
2009-02-23 10:21 ` Markus Metzger [this message]
2009-02-22 16:15 ` KOSAKI Motohiro
2009-02-22 16:23 ` Frederic Weisbecker
2009-02-22 19:29 ` Sam Ravnborg
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=a430082a0902230221p4f128073id93b5d5d4184ddf1@mail.gmail.com \
--to=markus.t.metzger@googlemail.com \
--cc=akpm@linux-foundation.org \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=markus.t.metzger@gmail.com \
--cc=mingo@elte.hu \
--cc=rakib.mullick@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
all inboxes | Powered by JetHome®