Re: [patch] i386: entry.s::error_code is not safe for kprobes

On Thursday 03 August 2006 12:20, Chuck Ebbert wrote:
> Because code marked unsafe for kprobes jumps directly to
> entry.S::error_code, that must be marked unsafe as well.
> The easiest way to do that is to move the page fault entry
> point to just before error_code and let it inherit the same
> section.
> 
> Also moved all the ".previous" asm directives for kprobes
> sections to column 1 and removed ".text" from them.

Ok added thanks

-Andi
-
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/

---

• References:
  • [patch] i386: entry.s::error_code is not safe for kprobes
    • From: Chuck Ebbert <[email protected]>

• Prev by Date: Re: [RFC, PATCH 0/5] Going forward with Resource Management - A cpu controller
• Next by Date: Re: problems with e1000 and jumboframes
• Previous by thread: Re: [patch] i386: entry.s::error_code is not safe for kprobes
• Next by thread: [PATCH] tty: add ioctl for setting the throttle threshold (handshake)
• 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]