linux-kernel - Re: [RFC] [PATCH] selective signal ptracing

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 for Android: free password hash cracker in your pocket

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

Date:	Sat, 16 Jun 2007 18:29:52 -0700 (PDT)
From:	Roland McGrath <roland@...hat.com>
To:	Benjamin Herrenschmidt <benh@...nel.crashing.org>
Cc:	Alan Cox <alan@...rguk.ukuu.org.uk>, john.blackwood@...r.com,
	linux-kernel@...r.kernel.org,
	Sven-Thorsten Dietrich <sdietrich@...ell.com>, bugsy@...r.com
Subject: Re: [RFC] [PATCH] selective signal ptracing

> What are the issues with arch like ARM ? 

The interesting class ARM belongs to is machines that don't (or don't
always) have hardware support for single-step.  Maintaining the status quo
of how PTRACE_SINGLESTEP functions on these machines is different in
implementation under utrace than it is for machines that always use
hardware support.  That is the only special complication for ARM, and it is
not really very complicated.  Apparently the way I described the issue in
the past was easily misunderstood.

> Also, is there a mail thread or paper somewhere describing utrace, its
> interfaces and what's needed to hook it up on a platform ?

See http://redhat.com/~roland/utrace/ for the patches and a porting howto.
The patches add a Documentation/ file and kerneldoc stuff for the interfaces.

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