From: "Vegard Nossum" <vegard.nossum@gmail.com>
To: "Alan Cox" <alan@lxorguk.ukuu.org.uk>
Cc: "Alexey Dobriyan" <adobriyan@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: [RFC][PATCH] sysrq-j: emergency shell
Date: Sat, 22 Nov 2008 23:48:46 +0100 [thread overview]
Message-ID: <19f34abd0811221448p34770633keb5ea97f8e9bf62d@mail.gmail.com> (raw)
In-Reply-To: <20081122190719.3ef24df6@lxorguk.ukuu.org.uk>
On Sat, Nov 22, 2008 at 8:07 PM, Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
>> > It seems that keyboard input will go to the shell only half of the
>> > time; the other half goes to whatever program was running there in
>> > the first place. I tried to kill the other users of the TTY using
>> > TIOCSCTTY, but it seems not to have worked. Any ideas?
>>
>> This should go in together with CVE number attached.
>
> TIOCSTTY isn't supposed to kill anything.
Oops, by killing, I meant simply to take it exclusively:
EPERM, unless the caller is root and arg equals 1, in which case
the tty is stolen, and all processes that had it as controlling
tty lose it.
But I realize that this does not necessarily mean that the other
processes cannot read from or write to the tty anymore. Do you know
how to do that? :-)
Vegard
--
"The animistic metaphor of the bug that maliciously sneaked in while
the programmer was not looking is intellectually dishonest as it
disguises that the error is the programmer's own creation."
-- E. W. Dijkstra, EWD1036
next prev parent reply other threads:[~2008-11-22 22:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-21 23:51 Vegard Nossum
2008-11-22 0:42 ` Matt Keenan
2008-11-22 7:19 ` David Newall
2008-11-22 17:27 ` Alexey Dobriyan
2008-11-22 19:07 ` Alan Cox
2008-11-22 22:48 ` Vegard Nossum [this message]
2008-11-23 0:10 ` Alan Cox
2008-11-23 19:29 ` Andi Kleen
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=19f34abd0811221448p34770633keb5ea97f8e9bf62d@mail.gmail.com \
--to=vegard.nossum@gmail.com \
--cc=adobriyan@gmail.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®