Re: [PATCH] kprobes: bad manipulation of 2 byte opcode on x86_64

On Friday 19 May 2006 10:29, Richard J Moore wrote:
> Is there any possibility of a inducing a page fault when checking the
> second byte?

AFAIK instr is in the out of line instruction copy. Kernel would need
to be pretty broken already if that page faulted.

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

Follow-Ups:
- Re: [PATCH] kprobes: bad manipulation of 2 byte opcode on x86_64
  - From: Satoshi Oshima <[email protected]>

References:
- Re: [PATCH] kprobes: bad manipulation of 2 byte opcode on x86_64
  - From: Richard J Moore <[email protected]>

Prev by Date: Re: [PATCH] Change ll_rw_block() calls in JBD
Next by Date: Re: [PATCH] Change ll_rw_block() calls in JBD
Previous by thread: Re: [PATCH] kprobes: bad manipulation of 2 byte opcode on x86_64
Next by thread: Re: [PATCH] kprobes: bad manipulation of 2 byte opcode on 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]