DSPBRIDGE: don't use potential invalid pointer
PATCH 1/1 DSPBRIDGE: don't use potential invalid pointer
From: Andy Shevchenko <[email protected]>
Signed-off-by Andy Shevchenko <[email protected]>
--- drivers/dsp/bridge/rmgr/proc.c | 1 + 1 files changed, 1 insertions(+), 0 deletions(-)
drivers/dsp/bridge/rmgr/proc.c +1 -0
@@ -323,6 +323,7 @@ PROC_Attach(u32 uProcessor, OPTIONAL CONST struct DSP_PROCESSORATTRIN *pAttrIn,"PROC_Attach: Could not allocate " "storage for notification \n");MEM_FreeObject (pProcObject); + goto func_end; }#ifndef RES_CLEANUP_DISABLE spin_lock (&pr_ctxt->proc_list_lock);
Signature · 1 line
1.5.6.5
Good,
Quoted 36 lines
-----Original Message-----
From: [email protected] [mailto:linux-omap- [email protected]] On Behalf Of Andy Shevchenko
Sent: Monday, September 07, 2009 3:03 AM
To: [email protected]
Cc: Andy Shevchenko
Subject: [PATCH 1/1] DSPBRIDGE: don't use potential invalid pointerFrom: Andy Shevchenko <[email protected]>
Signed-off-by Andy Shevchenko <[email protected]>---
drivers/dsp/bridge/rmgr/proc.c| 1 +1 files changed, 1 insertions(+), 0 deletions(-)drivers/dsp/bridge/rmgr/proc.c +1
-0@@ -323,6 +323,7 @@ PROC_Attach(u32 uProcessor, OPTIONAL CONST structDSP_PROCESSORATTRIN *pAttrIn,"PROC_Attach: Could not allocate " "storage for notification \n");MEM_FreeObject (pProcObject); + goto func_end; }#ifndef RES_CLEANUP_DISABLE spin_lock(&pr_ctxt->proc_list_lock);--
1.5.6.5--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html