From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Jon Smirl <jonsmirl@gmail.com>
Cc: Paul Fulghum <paulkf@microgate.com>,
lkml <linux-kernel@vger.kernel.org>,
"Theodore Ts'o" <tytso@mit.edu>
Subject: Re: tty_mutex and tty_old_pgrp
Date: Wed, 28 Jun 2006 19:04:25 +0100 [thread overview]
Message-ID: <1151517865.15166.54.camel@localhost.localdomain> (raw)
In-Reply-To: <9e4733910606281036k53956aaev3d323fbb7a2cb7a9@mail.gmail.com>
Ar Mer, 2006-06-28 am 13:36 -0400, ysgrifennodd Jon Smirl:
> This selinux code is checking to see if the current process still has
> access rights to it's controlling tty, right? If it doesn't tty and
> tty_old_pgrp are nulled out. Does this need locking?
Yes that looks like it needs to the tty lock covering it.
next prev parent reply other threads:[~2006-06-28 17:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-26 22:38 tty_mutex and tty_old_pgrp Jon Smirl
2006-06-27 22:56 ` Paul Fulghum
2006-06-28 3:29 ` Jon Smirl
2006-06-28 10:24 ` Alan Cox
2006-06-28 17:36 ` Jon Smirl
2006-06-28 18:04 ` Alan Cox [this message]
2006-06-28 18:13 ` Jon Smirl
2006-06-29 5:41 ` Jon Smirl
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=1151517865.15166.54.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=jonsmirl@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paulkf@microgate.com \
--cc=tytso@mit.edu \
/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