Sergio Lopez, le Tue 27 Sep 2011 15:27:55 +0200, a écrit :
> In that case, until GNU Mach is ported to 64 bits, a patch like this
> should be considered:
>
> * ipc/ipc_kmsg.c (ipc_kmsg_copyin_body): Change length type to
> unsigned64_t. Cast number to unsigned64_t.
> (ipc_kmsg_copyout_body): Likew
Sergio López, le Tue 27 Sep 2011 15:52:51 +0200, a écrit :
> Interrupting a thread without a continuation, puts it in a
> inconsistent state. This is the cause for the bug described in
> https://lists.gnu.org/archive/html/bug-hurd/2011-09/msg00148.html
Applied, thanks.
Samuel
2011/9/22 :
> Hi,
>
> While shutting down a subhurd today, I encounted a Mach panic; and I
> already encountered a rather similar one once a couple of months ago.
> (Might also have been while shutting down subhurd, but I can't say for
> sure anymore.) I'm attaching both traces -- perhaps someone
2011/9/23 :
> Hi,
>
> On Wed, Aug 10, 2011 at 02:10:22AM +0200, Samuel Thibault wrote:
>
>> I've digged a bit in the libdiskfs syncing issue at shutdown. The
>> scenario is the following:
>>
>> - halt or reboot is issued
>> - S_startup_reboot() gets called in init which
>> - calls reboot_system(
Interrupting a thread without a continuation, puts it in a
inconsistent state. This is the cause for the bug described in
https://lists.gnu.org/archive/html/bug-hurd/2011-09/msg00148.html
* kern/thread.c (thread_suspend): Fail with KERN_FAILURE if thread is
uninterruptible.
---
kern/thread.c |
El Fri, 23 Sep 2011 18:28:19 -0700
"Thomas Bushnell, BSG" escribió:
> I think the fear is of resource exhaustion, but there are so many of
> those problems, this would not be the first place to look IMO.
>
> Thomas
>
> On Thu, Sep 22, 2011 at 4:29 PM, Roland McGrath
> wrote:
>
> > The whole po
