From: Kirill Tkhai <ktkhai@virtuozzo.com>
To: gregkh@linuxfoundation.org, jslaby@suse.com, oleg@redhat.com,
ebiederm@xmission.com, ktkhai@virtuozzo.com
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH v2 1/3] Revert "do_SAK: Don't recursively take the tasklist_lock"
Date: Wed, 17 Jan 2018 15:39:32 +0300 [thread overview]
Message-ID: <151619277281.5683.16110625178528288163.stgit@localhost.localdomain> (raw)
In-Reply-To: <151619233415.5683.18062849657787533510.stgit@localhost.localdomain>
This reverts commit 20ac94378de5.
send_sig() does not take tasklist_lock for a long time,
so this commit and the problem it solves are not relevant
anymore.
Also, the problem of force_sig() is it clears SIGNAL_UNKILLABLE
flag, thus even global init may be killed by __do_SAK(),
which is definitely not the expected behavior.
Came from discussion in "tty: Iterate only thread group leaders in __do_SAK()"
https://lkml.org/lkml/2018/1/11/492
Suggested-by: Oleg Nesterov <oleg@redhat.com>
Signed-off-by: Kirill Tkhai <ktkhai@virtuozzo.com>
---
drivers/tty/tty_io.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/tty/tty_io.c b/drivers/tty/tty_io.c
index dc60aeea87d8..84715ba1aee2 100644
--- a/drivers/tty/tty_io.c
+++ b/drivers/tty/tty_io.c
@@ -2737,7 +2737,7 @@ void __do_SAK(struct tty_struct *tty)
if (i != 0) {
tty_notice(tty, "SAK: killed process %d (%s): by fd#%d\n",
task_pid_nr(p), p->comm, i - 1);
- force_sig(SIGKILL, p);
+ send_sig(SIGKILL, p, 1);
}
task_unlock(p);
} while_each_thread(g, p);
next prev parent reply other threads:[~2018-01-17 12:39 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-17 12:39 [PATCH v2 0/3] tty: Make __do_SAK() less greedy in regard to tasklist_lock Kirill Tkhai
2018-01-17 12:39 ` Kirill Tkhai [this message]
2018-01-17 17:18 ` [PATCH v2 1/3] Revert "do_SAK: Don't recursively take the tasklist_lock" Eric W. Biederman
2018-01-17 17:34 ` Oleg Nesterov
2018-01-17 17:49 ` Eric W. Biederman
2018-01-17 18:04 ` Oleg Nesterov
2018-01-17 18:37 ` Eric W. Biederman
2018-01-17 20:43 ` Oleg Nesterov
2018-01-18 10:07 ` Kirill Tkhai
2018-01-18 9:59 ` Kirill Tkhai
2018-01-17 12:39 ` [PATCH v2 2/3] tty: Avoid threads files iterations in __do_SAK() Kirill Tkhai
2018-01-17 12:39 ` [PATCH v2 3/3] tty: Use RCU read lock to iterate tasks and threads " Kirill Tkhai
2018-01-17 16:54 ` Eric W. Biederman
2018-01-17 17:39 ` Oleg Nesterov
2018-01-18 10:11 ` Kirill Tkhai
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=151619277281.5683.16110625178528288163.stgit@localhost.localdomain \
--to=ktkhai@virtuozzo.com \
--cc=ebiederm@xmission.com \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oleg@redhat.com \
/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®