From: Omar Ramirez Luna <omar.ramirez@ti.com>
To: Ameya Palande <ameya.palande@nokia.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"felipe.contreras@nokia.com" <felipe.contreras@nokia.com>,
"Menon, Nishanth" <nm@ti.com>,
"Chitriki Rudramuni, Deepak" <deepak.chitriki@ti.com>,
"Guzman Lugo, Fernando" <x0095840@ti.com>
Subject: Re: [PATCH 3/4] DSPBRIDGE: Fix memory corruption in DRV_ProcFreeDMMRes
Date: Tue, 23 Feb 2010 10:23:53 -0600 [thread overview]
Message-ID: <4B840119.10407@ti.com> (raw)
In-Reply-To: <9fb63d8737768758ac367ff242c4142f38ce7427.1266503387.git.ameya.palande@nokia.com>
On 2/18/2010 8:40 AM, Ameya Palande wrote:
> This patch fixes following issues:
>
> 1. pDMMRes was dereferenced and modified when it was already freed by
> PROC_Ummap(). This results in memory corruption.
>
> 2. Instead of passing ulDSPAddr, ulDSPResAddr was passed to PROC_UnMap()
> which will not retrieve correct DMMRes element.
>
> Signed-off-by: Ameya Palande<ameya.palande@nokia.com>
> Signed-off-by: Felipe Contreras<felipe.contreras@nokia.com>
> ---
> drivers/dsp/bridge/rmgr/drv.c | 12 ++----------
> 1 files changed, 2 insertions(+), 10 deletions(-)
>
Pushed to dspbridge
- omar
next prev parent reply other threads:[~2010-02-23 16:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-18 14:40 [PATCHv5 0/4] DSPBRIDGE: Improved reserved and mapped resource cleanup Ameya Palande
2010-02-18 14:40 ` [PATCH 1/4] DSPBRIDGE: Rename DMM_RES_OBJECT to DMM_MAP_OBJECT Ameya Palande
2010-02-23 16:23 ` Omar Ramirez Luna
2010-02-18 14:40 ` [PATCH 2/4] DSPBRIDGE: New reserved memory accounting framework Ameya Palande
2010-02-23 16:23 ` Omar Ramirez Luna
2010-02-18 14:40 ` [PATCH 3/4] DSPBRIDGE: Fix memory corruption in DRV_ProcFreeDMMRes Ameya Palande
2010-02-23 16:23 ` Omar Ramirez Luna [this message]
2010-02-18 14:40 ` [PATCH 4/4] DSPBRIDGE: Improved mapped memory cleanup Ameya Palande
2010-02-23 16:23 ` Omar Ramirez Luna
2010-02-18 18:16 ` [PATCHv5 0/4] DSPBRIDGE: Improved reserved and mapped resource cleanup Felipe Contreras
2010-02-18 22:46 ` Guzman Lugo, Fernando
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=4B840119.10407@ti.com \
--to=omar.ramirez@ti.com \
--cc=ameya.palande@nokia.com \
--cc=deepak.chitriki@ti.com \
--cc=felipe.contreras@nokia.com \
--cc=linux-omap@vger.kernel.org \
--cc=nm@ti.com \
--cc=x0095840@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.