From: Andries.Brouwer@cwi.nl
To: Andries.Brouwer@cwi.nl, alan@lxorguk.ukuu.org.uk
Cc: andrewm@uow.edu.au, linux-kernel@vger.kernel.org,
torvalds@transmeta.com, tytso@mit.edu
Subject: Re: [PATCH] more SAK stuff
Date: Mon, 2 Jul 2001 15:03:33 +0200 (MET DST) [thread overview]
Message-ID: <UTC200107021303.PAA496134.aeb@vlet.cwi.nl> (raw)
>> (a) It does less, namely will not kill processes with uid 0.
>> Ted, any objections?
Alan:
> That breaks the security guarantee. Suppose I use a setuid app to confuse
> you into doing something ?
On second thoughts I agree. Here is the patch without test for p->uid.
Andries
diff -u --recursive --new-file ../linux-2.4.6-pre8/linux/drivers/char/keyboard.c ./linux/drivers/char/keyboard.c
--- ../linux-2.4.6-pre8/linux/drivers/char/keyboard.c Mon Oct 16 21:58:51 2000
+++ ./linux/drivers/char/keyboard.c Mon Jul 2 13:28:09 2001
@@ -506,6 +506,8 @@
* them properly.
*/
+ if (!tty && ttytab && ttytab[0] && ttytab[0]->driver_data)
+ tty = ttytab[0];
do_SAK(tty);
reset_vc(fg_console);
#if 0
diff -u --recursive --new-file ../linux-2.4.6-pre8/linux/drivers/char/tty_io.c ./linux/drivers/char/tty_io.c
--- ../linux-2.4.6-pre8/linux/drivers/char/tty_io.c Sun Jul 1 15:19:26 2001
+++ ./linux/drivers/char/tty_io.c Mon Jul 2 14:53:52 2001
@@ -1818,20 +1818,29 @@
*
* Nasty bug: do_SAK is being called in interrupt context. This can
* deadlock. We punt it up to process context. AKPM - 16Mar2001
+ *
+ * Treat all VTs as a single tty for the purposes of SAK. A process with an
+ * open fd for one VT can do interesting things to all. aeb, 2001-07-02
*/
-static void __do_SAK(void *arg)
+#ifdef CONFIG_VT
+static inline int tty_is_vt(struct tty_struct *tty)
{
-#ifdef TTY_SOFT_SAK
- tty_hangup(tty);
+ return tty ? (tty->driver.type == TTY_DRIVER_TYPE_CONSOLE) : 0;
+}
#else
- struct tty_struct *tty = arg;
+static inline int tty_is_vt(struct tty_struct *tty)
+{
+ return 0;
+}
+#endif
+
+static inline void tty_hard_SAK(struct tty_struct *tty)
+{
struct task_struct *p;
int session;
- int i;
- struct file *filp;
-
- if (!tty)
- return;
+ int i;
+ struct file *filp;
+
session = tty->session;
if (tty->ldisc.flush_buffer)
tty->ldisc.flush_buffer(tty);
@@ -1839,7 +1848,9 @@
tty->driver.flush_buffer(tty);
read_lock(&tasklist_lock);
for_each_task(p) {
+ /* all VTs are considered a single tty here */
if ((p->tty == tty) ||
+ (tty_is_vt(tty) && tty_is_vt(p->tty)) ||
((session > 0) && (p->session == session))) {
send_sig(SIGKILL, p, 1);
continue;
@@ -1850,7 +1861,9 @@
for (i=0; i < p->files->max_fds; i++) {
filp = fcheck_files(p->files, i);
if (filp && (filp->f_op == &tty_fops) &&
- (filp->private_data == tty)) {
+ (filp->private_data == tty ||
+ (tty_is_vt(tty) &&
+ tty_is_vt(filp->private_data)))) {
send_sig(SIGKILL, p, 1);
break;
}
@@ -1860,6 +1873,17 @@
task_unlock(p);
}
read_unlock(&tasklist_lock);
+}
+
+static void __do_SAK(void *arg)
+{
+ struct tty_struct *tty = arg;
+ if (!tty) /* impossible */
+ return;
+#ifdef TTY_SOFT_SAK
+ tty_hangup(tty);
+#else
+ tty_hard_SAK(tty);
#endif
}
@@ -1872,6 +1896,8 @@
*/
void do_SAK(struct tty_struct *tty)
{
+ if (!tty)
+ return;
PREPARE_TQUEUE(&tty->SAK_tq, __do_SAK, tty);
schedule_task(&tty->SAK_tq);
}
next reply other threads:[~2001-07-02 13:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-02 13:03 Andries.Brouwer [this message]
2001-08-03 18:40 ` Building multipart modules with subdirectories Steven J. Hill
2001-08-04 10:30 ` Keith Owens
-- strict thread matches above, loose matches on Subject: below --
2001-07-02 12:49 [PATCH] more SAK stuff Andries.Brouwer
2001-07-02 12:16 Andries.Brouwer
2001-07-02 12:33 ` Alan Cox
2001-07-02 19:10 ` Hua Zhong
2001-07-03 22:00 ` Rob Landley
2001-07-06 1:45 ` Albert D. Cahalan
2001-07-02 18:57 ` Kain
2001-07-06 22:02 ` David Wagner
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=UTC200107021303.PAA496134.aeb@vlet.cwi.nl \
--to=andries.brouwer@cwi.nl \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=andrewm@uow.edu.au \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.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