[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.LFD.2.00.0905281417500.3397@localhost.localdomain>
Date: Thu, 28 May 2009 14:22:17 +0200 (CEST)
From: Thomas Gleixner <tglx@...utronix.de>
To: Paul Mundt <lethal@...ux-sh.org>
cc: Peter Zijlstra <peterz@...radead.org>,
Daniel Walker <dwalker@...o99.com>,
Linus Walleij <linus.ml.walleij@...il.com>,
Ingo Molnar <mingo@...e.hu>,
Andrew Victor <linux@...im.org.za>,
Haavard Skinnemoen <hskinnemoen@...el.com>,
Andrew Morton <akpm@...ux-foundation.org>,
linux-kernel@...r.kernel.org, linux-sh@...r.kernel.org,
linux-arm-kernel@...ts.arm.linux.org.uk,
John Stultz <johnstul@...ux.vnet.ibm.com>
Subject: Re: [PATCH] sched: Support current clocksource handling in fallback
sched_clock().
On Thu, 28 May 2009, Paul Mundt wrote:
> @@ -437,10 +441,19 @@ void clocksource_unregister(struct clocksource *cs)
> unsigned long flags;
>
> spin_lock_irqsave(&clocksource_lock, flags);
> +
> + if (sched_clocksource == cs) {
> + printk(KERN_WARNING "Refusing to unregister "
> + "scheduler clocksource %s", cs->name);
Hmm, isn't that dangerous ? The clocksource might be in a module or
in kmalloced memory which is going to be freed.
Thanks,
tglx
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists