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, 11 Sep 2014 13:42:20 -0700
From:	"Luis R. Rodriguez" <>
To:	Dmitry Torokhov <>
Cc:	James Bottomley <>,
	Tejun Heo <>,
	Lennart Poettering <>,
	Kay Sievers <>,
	Greg Kroah-Hartman <>,
	Wu Zhangjin <>, Takashi Iwai <>,
	Arjan van de Ven <>,
	"" <>,
	Oleg Nesterov <>,,
	Andrew Morton <>,
	Tetsuo Handa <>,
	Joseph Salisbury <>,
	Benjamin Poirier <>,
	Santosh Rastapur <>,
	One Thousand Gnomes <>,
	Tim Gardner <>,
	Pierre Fersing <>,
	Nagalakshmi Nandigama <>,
	Praveen Krishnamoorthy <>,
	Sreekanth Reddy <>,
	Abhijit Mahajan <>,
	Cas ey Leedom <>,
	Hariprasad S <>,,
	Linux SCSI List <>,
	"" <>
Subject: Re: [RFC v2 3/6] kthread: warn on kill signal if not OOM

On Thu, Sep 11, 2014 at 1:23 PM, Dmitry Torokhov
<> wrote:
>>  There are elements in common, but by and
>> large the biggest headaches at least in large device number boots have
>> already been tackled by the enterprise crowd (they don't like their
>> S390's or 1024 core NUMA systems taking half an hour to come up).
> Please do not position this as a mostly solved large systems problem,
> For us it is touchpad detection stalling kernel for 0.5-1 sec. Which is
> a lot given that we boot in seconds.

Dmitry, would working on top of the aysnc series be reasonable? Then
we could address these as separate things which we'd build on top of.
The one aspect I see us needing to share is the "async probe universe
is OK" flag.

To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to
More majordomo info at

Powered by blists - more mailing lists