[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5829248.7R2q3V7fJ1@wuerfel>
Date: Thu, 05 Nov 2015 14:53:54 +0100
From: Arnd Bergmann <arnd@...db.de>
To: linux-arm-kernel@...ts.infradead.org
Cc: Yury Norov <ynorov@...iumnetworks.com>, catalin.marinas@....com,
linux-kernel@...r.kernel.org, pinskia@...il.com,
Prasun.Kapoor@...iumnetworks.com, Nathan_Lynch@...tor.com,
agraf@...e.de, klimov.linux@...il.com,
Andrew Pinski <Andrew.Pinski@...iumnetworks.com>,
broonie@...nel.org, jan.dakinevich@...il.com,
Andrew Pinski <apinski@...ium.com>, ddaney.cavm@...il.com,
bamvor.zhangjian@...wei.com, philipp.tomsich@...obroma-systems.com,
andrey.konovalov@...aro.org,
christoph.muellner@...obroma-systems.com
Subject: Re: [PATCH v6 11/17] ptrace: Allow compat to use the native siginfo
On Tuesday 03 November 2015 02:30:40 Yury Norov wrote:
> From: Andrew Pinski <apinski@...ium.com>
>
> Set COMPAT_USE_NATIVE_SIGINFO to be true for non AARCH32 tasks.
>
> With ARM64 ILP32 ABI, we want to use the non-compat
> siginfo as we want to simplify signal handling for this new ABI.
> This patch just adds a new define COMPAT_USE_NATIVE_SIGINFO and
> if it is true then read/write in the compat case as it was the
> non-compat case.
Why does this use compat_ptrace_request()? I assume there is
a good reason for it, but I'm surprised you don't use the native
64-bit ptrace syscall.
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/
Powered by blists - more mailing lists