From: Ameya Palande <ameya.palande@nokia.com>
To: "Contreras Felipe (Nokia-D/Helsinki)" <felipe.contreras@nokia.com>
Cc: "ext Guzman Lugo, Fernando" <x0095840@ti.com>,
linux-omap <linux-omap@vger.kernel.org>,
Omar Ramirez Luna <omar.ramirez@ti.com>,
Nishanth Menon <nm@ti.com>,
"Chitriki Rudramuni, Deepak" <deepak.chitriki@ti.com>,
"Carmody Phil.2 (EXT-Ixonos/Helsinki)"
<ext-phil.2.carmody@nokia.com>
Subject: Re: [PATCH] DSPBRIDGE: Prevent memory corruption in DRV_ProcFreeDMMRes
Date: Thu, 11 Feb 2010 20:44:05 +0200 [thread overview]
Message-ID: <1265913845.26446.3.camel@sanganak> (raw)
In-Reply-To: <20100211155322.GE4673@annwn.felipec.org>
Hi all,
On Thu, 2010-02-11 at 16:53 +0100, Contreras Felipe (Nokia-D/Helsinki)
wrote:
> On Wed, Feb 10, 2010 at 06:31:35PM +0100, ext Guzman Lugo, Fernando wrote:
> > >-----Original Message-----
> > >From: Felipe Contreras [mailto:felipe.contreras@nokia.com]
> > >> Resource cleanup does not support that even without my proposed changes.
> > >
> > >Aha! I suspected it :P
> > >
> > Resource cleanup does not support that because it tries to unreserved
> > every chunk mapped. However it does not means the dspbridge does not
> > support reserving a big chunk of memory and mapping small parts of
> > that memory, but I have not tested it to confirm if it works.
>
> I think I did once and it didn't work, but I thought the problem was in
> my app. Anyway I think we should either forget about this use-case or
> fix the resource cleaning.
>
> > >> I just proposed a solution which fixes two issues in one patch.
> > >> Moreover if this change is merged when the second issue be fixed this
> > >> patch will not needed anymore, so why don't merge the patch which
> > >> fixes both errors at this moment?
> > >
> > >simple patches > complicated patches
> > The patch is more simple than it looks.
>
> Only one way to know :)
>
> > >Personally I think your patches should be a continuation to the patches
> > >I just proposed.
> > Yes, I think it would be better.
>
> Cool.
>
Thanks for reviewing the patch!
After going through your comments I feel the current patch is inadequate
to do proper resource cleanup :(
I am working on something which should take care of map and reserve
both. Basically I am working on separating current DMM resource
accounting for map and reserve, which should fix all the problems. Will
post the patchset soon!
Cheers,
Ameya.
prev parent reply other threads:[~2010-02-11 18:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-08 20:25 [PATCH] DSPBRIDGE: Prevent memory corruption in DRV_ProcFreeDMMRes Ameya Palande
2010-02-09 12:29 ` Felipe Contreras
2010-02-09 20:22 ` Guzman Lugo, Fernando
2010-02-09 23:48 ` Felipe Contreras
2010-02-10 4:06 ` Guzman Lugo, Fernando
2010-02-10 13:07 ` Felipe Contreras
2010-02-10 17:31 ` Guzman Lugo, Fernando
2010-02-11 15:53 ` Felipe Contreras
2010-02-11 18:44 ` Ameya Palande [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=1265913845.26446.3.camel@sanganak \
--to=ameya.palande@nokia.com \
--cc=deepak.chitriki@ti.com \
--cc=ext-phil.2.carmody@nokia.com \
--cc=felipe.contreras@nokia.com \
--cc=linux-omap@vger.kernel.org \
--cc=nm@ti.com \
--cc=omar.ramirez@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox