linux-kernel - Re: [PATCH 1/2] signals: kill(-1) should only signal processes in the same namespace

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: <m1mykgtklc.fsf@frodo.ebiederm.org>
Date:	Thu, 17 Jul 2008 11:46:23 -0700
From:	ebiederm@...ssion.com (Eric W. Biederman)
To:	sukadev@...ibm.com
Cc:	Daniel Hokka Zakrisson <daniel@...ac.com>,
	linux-kernel@...r.kernel.org,
	containers@...ts.linux-foundation.org, xemul@...nvz.org,
	oleg@...sign.ru, akpm@...ux-foundation.org, ebiederm@...ssion.com
Subject: Re: [PATCH 1/2] signals: kill(-1) should only signal processes in the same namespace

sukadev@...ibm.com writes:
>

> Like Pavel said, we had couple of attempts to fix the larger problem of
> signal semantics in containers but did not have a consensus on handling
> blocked/unhandled signals to container-init.

Oh.  I thought we were pretty close then I or somebody ran out of steam.

> It would still be good to fix this "kill -1" problem.
>
> Eric had a slightly optimized interface, 'pid_in_pid_ns()' in following
> patchset. Maybe we could use that ?
>
> https://lists.linux-foundation.org/pipermail/containers/2007-December/009174.html

Eric

--
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/