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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <588FC7E2-C106-456A-81E7-A98F99F0E392@amazon.com>
Date:   Mon, 11 Jun 2018 23:47:46 +0000
From:   "Farnitano, Jarrett" <jmf@...zon.com>
To:     "Eric W. Biederman" <ebiederm@...ssion.com>
CC:     "kexec@...ts.infradead.org" <kexec@...ts.infradead.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] kexec: yield to scheduler when loading kimage segments

> On 6/11/18, 4:00 PM, "Eric W. Biederman" <ebiederm@...ssion.com> wrote:
> 
>     Is there a practical problem with unresponsiveness?  You are talking
>     an embedded machine and rarely are there people in front of embedded
>     computers these days.

I did run into a practical problem. Hardware watchdogs on embedded systems can have short timers on the order of seconds. If the system is locked up for a few seconds with only a single core available, the watchdog may not be pet in a timely fashion. If this happens, the hardware watchdog will fire and reset the system.

This really only becomes a problem when you are working with a single core, a decently sized initrd, and have a constrained hardware watchdog.  

Jarrett

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ