linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marc-Christian Petersen <m.c.p@wolk-project.de>
To: Marcelo Tosatti <marcelo@conectiva.com.br>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: [PATCH 2.4.22-pre10] SAK: If a process is killed by SAK, give us an info about which one was killed
Date: Fri, 1 Aug 2003 12:40:23 +0200	[thread overview]
Message-ID: <200307312254.16964.m.c.p@wolk-project.de> (raw)

[-- Attachment #1: Type: text/plain, Size: 92 bytes --]

Hi Marcelo,

$subject says it all.

Please apply for 2.4.22-pre10. Thank you :)

ciao, Marc

[-- Attachment #2: 2.4-SAK-info.patch --]
[-- Type: text/x-diff, Size: 698 bytes --]

--- a/drivers/char/tty_io.c	Fri Jan 25 15:49:44 2002
+++ b/drivers/char/tty_io.c	Tue Mar 19 08:28:27 2002
@@ -1888,6 +1888,9 @@
	for_each_task(p) {
		if ((p->tty == tty) ||
		    ((session > 0) && (p->session == session))) {
+				printk(KERN_NOTICE "SAK: killed process %d"
+				" (%s): p->session==tty->session\n",
+				p->pid, p->comm);
			send_sig(SIGKILL, p, 1);
			continue;
		}
@@ -1898,6 +1898,9 @@
				filp = fcheck_files(p->files, i);
				if (filp && (filp->f_op == &tty_fops) &&
				    (filp->private_data == tty)) {
+						printk(KERN_NOTICE "SAK: killed process %d"
+						" (%s): fd#%d opened to the tty\n",
+						p->pid, p->comm, i);
					send_sig(SIGKILL, p, 1);
					break;
				}

             reply	other threads:[~2003-08-01 10:46 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-01 10:40 Marc-Christian Petersen [this message]
2003-08-01 12:09 ` [PATCH 2.4.22-pre10] SAK: If a process is killed by SAK, give us an info about which one was killed Alan Cox
2003-08-01 12:26   ` Marc-Christian Petersen
2003-08-01 12:38     ` Marc-Christian Petersen
2003-08-01 12:57     ` Alan Cox
2003-08-05 10:59   ` Pavel Machek
2003-08-05 16:38     ` Alan Cox
2003-08-05 17:09       ` Pavel Machek

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=200307312254.16964.m.c.p@wolk-project.de \
    --to=m.c.p@wolk-project.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo@conectiva.com.br \
    /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;
as well as URLs for NNTP newsgroup(s).