linux-kernel - getter PTRACE_GETSIGINFO should not modify anything [Re: [PATCH 11/11] ptrace: implement group stop notification for ptracer]

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20110515140232.GB31855@host1.jankratochvil.net>
Date:	Sun, 15 May 2011 16:02:32 +0200
From:	Jan Kratochvil <jan.kratochvil@...hat.com>
To:	Tejun Heo <tj@...nel.org>
Cc:	oleg@...hat.com, vda.linux@...glemail.com,
	linux-kernel@...r.kernel.org, torvalds@...ux-foundation.org,
	akpm@...ux-foundation.org, indan@....nu
Subject: getter PTRACE_GETSIGINFO should not modify anything  [Re: [PATCH
 11/11] ptrace: implement group stop notification for ptracer]

On Sun, 08 May 2011 17:49:05 +0200, Tejun Heo wrote:
> which triggers INTERRUPT trap but is sticky until the next
> PTRACE_GETSIGINFO.

PTRACE_GETSIGINFO is a getter.  It must not modify anything.  Or there should
be some other way how to query the siginfo_t state fully transparently (*).

(*) But if there exists such syscall it probably does not make sense to modify
    anything by PTRACE_GETSIGINFO.

Imagine various LD_PRELOAD tools which try to wrap system/library calls and
operate with ptrace while keeping it transparent for the original debugger.
(I have a bunch of such libraries for testing gdb/strace/etc. written there.)

Also complicated debuggers with internal OO hierarchy would need to just wrap
PTRACE_GETSIGINFO into an internal function to make it transparent for calls
not intending to modify the debuggee state.

Thanks,
Jan
--
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/