linux-kernel - Re: powerpc: syscall_dotrace() && retcode (Was: powerpc: fork && stepping)

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:	Wed, 02 Dec 2009 07:17:47 +1100
From:	Benjamin Herrenschmidt <benh@...nel.crashing.org>
To:	Roland McGrath <roland@...hat.com>
Cc:	Oleg Nesterov <oleg@...hat.com>,
	Ananth N Mavinakayanahalli <ananth@...ibm.com>,
	Veaceslav Falico <vfalico@...hat.com>,
	Paul Mackerras <paulus@...ba.org>,
	Alexey Dobriyan <adobriyan@...il.com>,
	Christoph Hellwig <hch@...radead.org>,
	"Frank Ch. Eigler" <fche@...hat.com>, Ingo Molnar <mingo@...e.hu>,
	Peter Zijlstra <peterz@...radead.org>,
	linux-kernel@...r.kernel.org, utrace-devel@...hat.com,
	Jan Kratochvil <jan.kratochvil@...hat.com>
Subject: Re: powerpc: syscall_dotrace() && retcode (Was: powerpc: fork &&
 stepping)

On Tue, 2009-12-01 at 11:27 -0800, Roland McGrath wrote:
> 
> If the powerpc maintainers want to change the behavior here, that is fine
> by me.  But there is no need for that just to satisfy general ptrace
> cleanups (or utrace).  Normal concerns require that no such change break
> the ptrace behavior that userland could have relied on in the past.
> 
> So off hand I don't see a reason to change at all.  If every arch were to
> change so that registers changed at syscall-entry were left unmolested by
> aborting the syscall, then that might be a new consistency worth having.
> But short of that, I don't really see a benefit.
> 
> All this implies that the ptrace-tests case relating to this needs to be
> tailored differently for powerpc and each other arch so it expects and
> verifies exactly the arch-specific behavior that's been seen in the past. 

Ok thanks. I'm happy to not change it then, the risk of breaking some
existing assumption is too high in my book.

Cheers,
Ben.


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