From: Ameya Palande <ameya.palande@nokia.com>
To: "Kanigeri, Hari" <h-kanigeri2@ti.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: find_task_by_vpid() not protected
Date: Tue, 31 Mar 2009 17:51:42 +0300 [thread overview]
Message-ID: <49D22DFE.7070105@nokia.com> (raw)
Hi Hari,
I found out that bridge_open() function is calling find_task_by_vpid()
without taking rcu_read_lock() or with tasklist_lock read-held.
Should we introduce proper read locking with following functions?
read_lock(&tasklist_lock);
read_unlock(&tasklist_lock);
Cheers,
Ameya.
reply other threads:[~2009-03-31 14:51 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=49D22DFE.7070105@nokia.com \
--to=ameya.palande@nokia.com \
--cc=h-kanigeri2@ti.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 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.