From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jiri Kosina Subject: Re: [RFC v2 3/6] kthread: warn on kill signal if not OOM Date: Wed, 10 Sep 2014 00:00:31 +0200 (CEST) Message-ID: References: <1409899047-13045-1-git-send-email-mcgrof@do-not-panic.com> <20140905141241.GC10455@mtj.dyndns.org> <20140905164405.GA28964@core.coreip.homeip.net> <20140905174925.GA12991@mtj.dyndns.org> <20140905224047.GC15723@mtj.dyndns.org> <20140909011059.GB11706@mtj.dyndns.org> <1410241109.2028.22.camel@jarvis.lan> Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: James Bottomley , Tejun Heo , Lennart Poettering , Kay Sievers , Dmitry Torokhov , Greg Kroah-Hartman , Wu Zhangjin , Takashi Iwai , Arjan van de Ven , "linux-kernel@vger.kernel.org" , Oleg Nesterov , hare@suse.com, Andrew Morton , Tetsuo Handa , Joseph Salisbury , Benjamin Poirier , Santosh Rastapur , One Thousand Gnomes , Tim Gardner , Pierre Fersing , Nagalakshmi Nandigama Return-path: Received: from cantor2.suse.de ([195.135.220.15]:57333 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751950AbaIIWAm (ORCPT ); Tue, 9 Sep 2014 18:00:42 -0400 In-Reply-To: Sender: netdev-owner@vger.kernel.org List-ID: On Tue, 9 Sep 2014, Luis R. Rodriguez wrote: > By design it seems systemd should not allow worker processes to block > indefinitely and in fact it currently uses the same timeout for all > types of worker processes. And I whole-heartedly believe this is something that fundamentally needs to be addressed in systemd, not in the kernel. This aproach is actually introducing a user-visible regressions. Look, for example, exec() never times out. Therefore if your system is on its knees, heavily overloaded (or completely broken), you are likely to be able to `reboot' it, because exec("/sbin/reboot") ultimately succeeds. But with all the timeouts, dbus, "Failed to issue method call: Did not receive a reply" messages, this is getting close to impossible. -- Jiri Kosina SUSE Labs