linux-kernel - Re: [PATCH 1/2] kprobes: Update document about irq disabled state in kprobe handler

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20100805125551.GA28884@in.ibm.com>
Date:	Thu, 5 Aug 2010 18:25:51 +0530
From:	Ananth N Mavinakayanahalli <ananth@...ibm.com>
To:	Masami Hiramatsu <masami.hiramatsu.pt@...achi.com>
Cc:	linux-kernel@...r.kernel.org, linux-doc@...r.kernel.org
Subject: Re: [PATCH 1/2] kprobes: Update document about irq disabled state
 in kprobe handler

On Thu, Aug 05, 2010 at 09:35:05PM +0900, Masami Hiramatsu wrote:
> Update kprobes.txt about interrupts disabled state inside
> kprobes handlers, because optimized probe/boosted kretprobe
> run without disabling interrrupts on x86.
> 
> Signed-off-by: Masami Hiramatsu <masami.hiramatsu.pt@...achi.com>
> Cc: Ananth N Mavinakayanahalli <ananth@...ibm.com>

Acked-by: Ananth N Mavinakayanahalli <ananth@...ibm.com>

> Cc: linux-kernel@...r.kernel.org
> Cc: linux-doc@...r.kernel.org
> ---
> 
>  Documentation/kprobes.txt |    8 +++++---
>  1 files changed, 5 insertions(+), 3 deletions(-)
> 
> diff --git a/Documentation/kprobes.txt b/Documentation/kprobes.txt
> index 6653017..4189f01 100644
> --- a/Documentation/kprobes.txt
> +++ b/Documentation/kprobes.txt
> @@ -541,9 +541,11 @@ Kprobes does not use mutexes or allocate memory except during
>  registration and unregistration.
> 
>  Probe handlers are run with preemption disabled.  Depending on the
> -architecture, handlers may also run with interrupts disabled.  In any
> -case, your handler should not yield the CPU (e.g., by attempting to
> -acquire a semaphore).
> +architecture and optimization state, handlers may also run with
> +interrupts disabled (e.g., kretprobe handlers and optimized kprobe
> +handlers run without interrupt disabled on x86/x86-64).  In any case,
> +your handler should not yield the CPU (e.g., by attempting to acquire
> +a semaphore).
> 
>  Since a return probe is implemented by replacing the return
>  address with the trampoline's address, stack backtraces and calls
> 
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/