From: Kevin Hilman <khilman@deeprootsystems.com>
To: "Mittal, Mukund" <mmittal@ti.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: [PATCH] OMAP: timer-gp: Fix for null pointer dereferencing issue
Date: Thu, 09 Jul 2009 08:04:23 -0700 [thread overview]
Message-ID: <87ws6hvqx4.fsf@deeprootsystems.com> (raw)
In-Reply-To: <EAF47CD23C76F840A9E7FCE10091EFAB02B565CD5B@dbde02.ent.ti.com> (Mukund Mittal's message of "Thu\, 9 Jul 2009 17\:09\:18 +0530")
"Mittal, Mukund" <mmittal@ti.com> writes:
> From: Mukund Mittal <mmittal@ti.com>
>
> OMAP: timer-gp: Fix for null pointer dereferencing issue
>
> There was a null pointer dereferencing issue for gpt pointer.
> It was checked and an error was printed but execution was not terminated.
> Fixed by calling function BUG().
I think BUG() is a bit drastic here. I think it should probably
WARN() and fail gracefully instead of grind to a screeching halt.
Kevin
> Signed-off-by: Mukund Mittal <mmittal@ti.com>
> ---
> arch/arm/mach-omap2/timer-gp.c | 14 +++++++-------
> 1 files changed, 7 insertions(+), 7 deletions(-)
>
> Index: linux-omap-2.6/arch/arm/mach-omap2/timer-gp.c
> ===================================================================
> --- linux-omap-2.6.orig/arch/arm/mach-omap2/timer-gp.c
> +++ linux-omap-2.6/arch/arm/mach-omap2/timer-gp.c
> @@ -205,14 +205,13 @@ static void __init omap2_gp_clocksource_
> {
> static struct omap_dm_timer *gpt;
> u32 tick_rate, tick_period;
> - static char err1[] __initdata = KERN_ERR
> - "%s: failed to request dm-timer\n";
> - static char err2[] __initdata = KERN_ERR
> - "%s: can't register clocksource!\n";
>
> gpt = omap_dm_timer_request();
> - if (!gpt)
> - printk(err1, clocksource_gpt.name);
> + if (!gpt) {
> + printk(KERN_ERR "%s: failed to request dm-timer\n",
> + clocksource_gpt.name);
> + BUG();
> + }
> gpt_clocksource = gpt;
>
> omap_dm_timer_set_source(gpt, OMAP_TIMER_SRC_SYS_CLK);
> @@ -224,7 +223,8 @@ static void __init omap2_gp_clocksource_
> clocksource_gpt.mult =
> clocksource_khz2mult(tick_rate/1000, clocksource_gpt.shift);
> if (clocksource_register(&clocksource_gpt))
> - printk(err2, clocksource_gpt.name);
> + printk(KERN_ERR "%s: can't register clocksource!\n",
> + clocksource_gpt.name);
> }
> #endif
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-omap" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2009-07-09 15:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-09 11:39 [PATCH] OMAP: timer-gp: Fix for null pointer dereferencing issue Mittal, Mukund
2009-07-09 15:04 ` Kevin Hilman [this message]
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=87ws6hvqx4.fsf@deeprootsystems.com \
--to=khilman@deeprootsystems.com \
--cc=linux-omap@vger.kernel.org \
--cc=mmittal@ti.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