linux-kernel - Re: [RFC Patch v1 33/55] ARC: ptrace support

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]

Message-Id: <201211151156.52033.arnd@arndb.de>
Date:	Thu, 15 Nov 2012 11:56:51 +0000
From:	Arnd Bergmann <arnd@...db.de>
To:	Vineet Gupta <Vineet.Gupta1@...opsys.com>
Cc:	linux-arch@...r.kernel.org, linux-kernel@...r.kernel.org,
	tglx@...utronix.de
Subject: Re: [RFC Patch v1 33/55] ARC: ptrace support

On Thursday 15 November 2012, Vineet Gupta wrote:
> On Monday 12 November 2012 07:21 PM, Arnd Bergmann wrote:
>
> > I think these should be moved into regsets, as we have done for all
> > other new architectures. Your arch_ptrace then becomes a trivial wrapper
> > around ptrace_request.
> 
> The regset stuff is already complete - and even this code uses the reget
> callbacks. It's just that we need to carry on this dual ABI for some
> time for our legacy gdbserver.

Ok, but please don't submit that patch upstream then. It's ok to
keep it in your own tree for the transitional phase, I assume
that you have other patches in there as well that are not submitted
yet. Once the new gdb is in use everywhere, you can just drop that
patch.

The problem with having this upstream is that this would create
a precedent for having the interface, and if people start relying
on it being there, we can't remove from upstream any more. If you
just have it in your private repository, we can just argue that it
was never officially supported.

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