linux-kernel - Re: malicious filesystems (was Re: [linux-pm] Re: [PATCH] Remove process freezer from suspend to RAM

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <E1IA3oR-0002wg-00@dorka.pomaz.szeredi.hu>
Date:	Sun, 15 Jul 2007 15:06:59 +0200
From:	Miklos Szeredi <miklos@...redi.hu>
To:	oleg@...sign.ru
CC:	rjw@...k.pl, pavel@....cz, linux-kernel@...r.kernel.org
Subject: Re: malicious filesystems (was Re: [linux-pm] Re: [PATCH] Remove process freezer from suspend to RAM

> > SIGKILL won't work on a stopped task.  Neither on a traced task.
> 
> Why do you think so? It works in both cases (ptracer can use
> PT_TRACE_EXIT, but the task is killed anyway).

Just from experience with tasks stuck in "T" state.  After for example
an UML dies, some of the processes only react to SIGCONT, but not to
SIGKILL.

I have no idea why this happens.

Miklos
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/