From: "Valdis Klētnieks" <valdis.kletnieks@vt.edu>
To: John Wood <john.wood@gmx.com>
Cc: kernelnewbies@kernelnewbies.org
Subject: Re: Notify special task kill using wait* functions
Date: Sun, 04 Apr 2021 17:10:25 -0400 [thread overview]
Message-ID: <193167.1617570625@turing-police> (raw)
In-Reply-To: <20210404094837.GA3263@ubuntu>
[-- Attachment #1.1: Type: text/plain, Size: 564 bytes --]
On Sun, 04 Apr 2021 11:48:37 +0200, John Wood said:
> that exec and the child crashes is mitigated. The only drawback here, as
> point Andi, is that a supervisor respawns some process killed. To avoid
> this situation he suggest to notify to usersapace via wait* that the
> task has been killed by "brute". Then, this supervisor has the chance to
> do what they need (respawn or not).
And how does the kernel know that it's notifying a "real" supervisor process,
and not a process started by the bad guy, who can receive the notification
and decide to respawn?
[-- Attachment #1.2: Type: application/pgp-signature, Size: 832 bytes --]
[-- Attachment #2: Type: text/plain, Size: 170 bytes --]
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
next prev parent reply other threads:[~2021-04-04 21:10 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-30 17:34 Notify special task kill using wait* functions John Wood
2021-03-30 18:40 ` Valdis Klētnieks
2021-04-02 12:49 ` John Wood
2021-04-03 3:50 ` Valdis Klētnieks
2021-04-03 7:02 ` John Wood
2021-04-03 21:34 ` Valdis Klētnieks
2021-04-04 9:48 ` John Wood
2021-04-04 21:10 ` Valdis Klētnieks [this message]
2021-04-05 7:31 ` John Wood
2021-04-06 23:55 ` Valdis Klētnieks
2021-04-07 17:51 ` John Wood
2021-04-07 20:38 ` Valdis Klētnieks
2021-04-08 1:51 ` Andi Kleen
2021-04-09 14:29 ` John Wood
2021-04-09 15:06 ` Andi Kleen
2021-04-09 16:08 ` John Wood
2021-04-09 23:28 ` Valdis Klētnieks
2021-04-11 8:46 ` John Wood
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=193167.1617570625@turing-police \
--to=valdis.kletnieks@vt.edu \
--cc=john.wood@gmx.com \
--cc=kernelnewbies@kernelnewbies.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;
as well as URLs for NNTP newsgroup(s).