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  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]
Date:	Thu, 16 Oct 2014 01:46:44 +0600
From:	"Alexander E. Patrakov" <>
To:	Anatol Pomozov <>,
	Tom Gundersen <>
CC:	One Thousand Gnomes <>,
	Takashi Iwai <>, Kay Sievers <>,
	Sreekanth Reddy <>,
	James Bottomley <>,
	Praveen Krishnamoorthy <>,
	hare <>,
	Nagalakshmi Nandigama <>,
	Wu Zhangjin <>,
	Tetsuo Handa <>,
	"mpt-fusionlinux.pdl" <>,
	Tim Gardner <>,
	Benjamin Poirier <>,
	Santosh Rastapur <>,
	Casey Leedom <>,
	Hariprasad S <>,
	Pierre Fersing <>,
	Arjan van de Ven <>,
	Abhijit Mahajan <>,
	systemd Mailing List <>,
	Linux SCSI List <>,
	"" <>,
	Dmitry Torokhov <>,
	Oleg Nesterov <>,
	"" <>,
	Tejun Heo <>,
	Andrew Morton <>,
	Joseph Salisbury <>
Subject: Re: [systemd-devel] [RFC v2 3/6] kthread: warn on kill signal if
 not OOM

16.10.2014 01:41, Anatol Pomozov wrote:
> True. module name should be enough. In this case to debug the issue user needs:
>   - disable failing udev rule (or blacklist module?)
>   - reboot, it will let the user get into shell
>   - modprobe the failing module
>   - use sysrq-trigger to get more information about stuck process

Nitpick: this only works only if the "stuck modprobe" bug is 100% 
reproducible. Which is not a given. So it is better to collect as much 
information about the bug when it is noticed by systemd.

Alexander E. Patrakov
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists