Re: Alarm execl failed on 2.6.12

I know it got fixed.
I want to know how it is fixed. Is there a patch for it?
Thanks
-Aubrey

2005/11/16, Alex Riesen <[email protected]>:
> On 11/16/05, Aubrey <[email protected]> wrote:
> > Running test can't stop in 3 seconds. But it should be.
> > Because the case can run properly on 2.6.11 and 2.6.13.
> > What difference about it?
>
> it was just broken and got fixed.
>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • Re: Alarm execl failed on 2.6.12
    • From: Alex Riesen <[email protected]>

• References:
  • Alarm execl failed on 2.6.12
    • From: Aubrey <[email protected]>

• Prev by Date: Re: pfn_to_nid under CONFIG_SPARSEMEM and CONFIG_NUMA
• Next by Date: Xorg is using MAP_PRIVATE, PROT_WRITE mprotect of VM_RESERVED memory
• Previous by thread: Alarm execl failed on 2.6.12
• Next by thread: Re: Alarm execl failed on 2.6.12
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]