linux-kernel - Re: utrace comments

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]

Date:	Mon, 30 Apr 2007 10:18:09 +0100
From:	Russell King <rmk+lkml@....linux.org.uk>
To:	Christoph Hellwig <hch@...radead.org>,
	Roland McGrath <roland@...hat.com>,
	Christoph Hellwig <hch@....de>, linux-kernel@...r.kernel.org,
	linux-arch@...r.kernel.org
Subject: Re: utrace comments

On Mon, Apr 30, 2007 at 10:08:40AM +0100, Christoph Hellwig wrote:
> Btw, is there a fundamental reason why an architecture would not support
> single-stepping except for a transition period of porting, i.e. are there
> real hardware limitation in any of our ports?

Roland's idea of single-stepping is that it *must* be supported by
hardware for utrace to use it.  There are a number of architectures
which can only do single-stepping by modifying the text of the
program being single stepped.  ARM is one such example.

As such, even when utrace is complete, some architectures will never
support in-kernel single step with utrace.  I believe Roland's idea
is to have single step supported on these via some vapourware userspace
library.

My biggest worry is that the architectures which do not support hardware
single stepping are seen by many people as "minority architectures" which
"don't really matter" and as such making support for a feature such a
special case will probably result in the feature effectively being
unavailable on those architectures.

As such I have zero motivation to continue my forrey into utrace from
a couple of months ago.  I'd also like to see utrace become *optional*
for architectures to support, rather than as it currently stands as
a *mandatory* requirement when merged.

-- 
Russell King
 Linux kernel    2.6 ARM Linux   - http://www.arm.linux.org.uk/
 maintainer of:
-
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/