Re: Tracking a bug in x86-64

On Thu, 16 Jun 2005, Bongani Hlope wrote:
>
> push 410, pop 205, pop 103, push 103, pop 51, pop 26, push 13, pop 6, push 4 and push 1
> This points to: randomisation-top-of-stack-randomization.patch

Goodie.

Can you verify (just to make doubly sure that there are no subtle
interactions anywhere) that the current top-of-tree with that _one_ patch
reverted ends up working for you?

Anyway, thanks a heap for spending the time narrowing this down!

		Linus
-
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: Tracking a bug in x86-64
    • From: Bongani Hlope <[email protected]>

• References:
  • Tracking a bug in x86-64
    • From: Bongani Hlope <[email protected]>
  • Re: Tracking a bug in x86-64
    • From: Linus Torvalds <[email protected]>
  • Re: Tracking a bug in x86-64
    • From: Andrew Morton <[email protected]>
  • Re: Tracking a bug in x86-64
    • From: Bongani Hlope <[email protected]>

• Prev by Date: Re: Tracking a bug in x86-64
• Next by Date: Re: Porting kref to a 2.4 kernel (2.4.20 or greater)
• Previous by thread: Re: Tracking a bug in x86-64
• Next by thread: Re: Tracking a bug in x86-64
• 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]