From: Eric Paris <eparis@redhat.com>
To: James Morris <jmorris@namei.org>
Cc: selinux@tycho.nsa.gov, sds@tycho.nsa.gov
Subject: Re: [PATCH] SELinux: hold tasklist_lock and siglock while waking wait_chldexit
Date: Tue, 04 Nov 2008 16:50:39 -0500 [thread overview]
Message-ID: <1225835439.3320.15.camel@localhost.localdomain> (raw)
In-Reply-To: <alpine.LRH.1.10.0811050845350.1992@tundra.namei.org>
On Wed, 2008-11-05 at 08:46 +1100, James Morris wrote:
> On Tue, 4 Nov 2008, Eric Paris wrote:
>
> > From: Eric Paris <eparis@redhat.com>
> >
> > SELinux has long been calling wake_up_interruptible() on
> > current->parent->signal->wait_chldexit without holding any locks. It
> > appears that this operation should hold the tasklist_lock to dereference
> > current->parent and we should hold the siglock when waking up the
> > signal->wait_chldexit.
> >
> > Signed-off-by: Eric Paris <eparis@redhat.com>
>
> This seems correct to me, too, although I'll just push it to
> security-testing#next at least for the moment so it gets some testing.
>
> How did you find this issue?
sds over there noticed that we weren't doing any locking during code
review and thought it looked off.
I've also poked roland privately to try to get him to take a gander.
Who else knows this locking well to tell me if I got it right?
-Eric
--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.
prev parent reply other threads:[~2008-11-04 21:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-04 20:18 [PATCH] SELinux: hold tasklist_lock and siglock while waking wait_chldexit Eric Paris
2008-11-04 21:46 ` James Morris
2008-11-04 21:50 ` Eric Paris [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=1225835439.3320.15.camel@localhost.localdomain \
--to=eparis@redhat.com \
--cc=jmorris@namei.org \
--cc=sds@tycho.nsa.gov \
--cc=selinux@tycho.nsa.gov \
/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.