linux-kernel - Re: [PATCH] pidns: reboot_pid_ns: use SEND_SIG_FORCED instead of force

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: <20120416153843.GA9302@redhat.com>
Date:	Mon, 16 Apr 2012 17:38:43 +0200
From:	Oleg Nesterov <oleg@...hat.com>
To:	Serge Hallyn <serge.hallyn@...onical.com>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	Daniel Lezcano <daniel.lezcano@...e.fr>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] pidns: reboot_pid_ns: use SEND_SIG_FORCED instead of
	force_sig()

On 04/16, Serge Hallyn wrote:
>
> Quoting Oleg Nesterov (oleg@...hat.com):
> >
> > Strange... I even tested this change, but only in the root namespace.
> > OK, thanks, I'll investigate. I hope you verified your kernel has
> > 629d362b commit ;)
>
> I took friday's HEAD of Linus tree.  All went fine.  Added this patch.
> The container can shutdown, but reboot causes shutdown.  Don't undersrtand
> why.

Heh. This looks "impossible". I'd like to understand the reason.
So, LINUX_REBOOT_CMD_RESTART results in WIFSIGNALED() == SIGINT?

OK, I'll try to test this patch in the non-root namespace.

Oleg.

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