From: Ameya Palande <ameya.palande@nokia.com>
To: "ext Ramos Falcon, Ernesto" <ernesto@ti.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"Contreras Felipe (Nokia-D/Helsinki)"
<felipe.contreras@nokia.com>,
"Doyu Hiroshi (Nokia-D/Helsinki)" <hiroshi.doyu@nokia.com>
Subject: Re: [PATCH] DSPBRIDGE: Validate Processor Handle from user
Date: Tue, 09 Feb 2010 19:26:43 +0200 [thread overview]
Message-ID: <1265736403.2832.6.camel@sanganak> (raw)
In-Reply-To: <B852767254C5C94EBB1040EE0EFA06008C89E954@dlee01.ent.ti.com>
Hi Ernesto,
On Tue, 2010-02-09 at 18:07 +0100, ext Ramos Falcon, Ernesto wrote:
> From 07b9f6d30c9d363ba0c4cefded8068662e1048c4 Mon Sep 17 00:00:00 2001
> From: Ernesto Ramos <ernesto@ti.com>
> Date: Wed, 3 Feb 2010 19:43:31 -0600
> Subject: [PATCH] DSPBRIDGE: Validate Processor Handle from user.
>
> Add check to validate the Processor handle received
> from user.
>
> Signed-off-by: Ernesto Ramos <ernesto@ti.com>
> ---
> drivers/dsp/bridge/pmgr/wcd.c | 86 ++++++++++++-
> drivers/dsp/bridge/rmgr/proc.c | 280 ++++++++++++++--------------------------
> 2 files changed, 179 insertions(+), 187 deletions(-)
My understanding: In bridge_open() we allocate a new process_context and
store it in filp->private_data which can't be modified / tampered by
user space.
If this understanding is correct, then why we need to perform any
validation on data hold be process_context pointer stored in
flip->private_data?
If you don't trust hProcessor handle received from user space arguments
then instead of using that we can just use pCtxt->hProcessor!
I don't understand why we need validation so NACK from my side.
Cheers,
Ameya.
next prev parent reply other threads:[~2010-02-09 17:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-09 17:07 [PATCH] DSPBRIDGE: Validate Processor Handle from user Ramos Falcon, Ernesto
2010-02-09 17:26 ` Ameya Palande [this message]
2010-02-09 17:51 ` Ramos Falcon, Ernesto
2010-02-11 13:47 ` Ameya Palande
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=1265736403.2832.6.camel@sanganak \
--to=ameya.palande@nokia.com \
--cc=ernesto@ti.com \
--cc=felipe.contreras@nokia.com \
--cc=hiroshi.doyu@nokia.com \
--cc=linux-omap@vger.kernel.org \
/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