summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorRussell King <rmk@dyn-67.arm.linux.org.uk>2006-06-15 18:00:34 +0100
committerRussell King <rmk+kernel@arm.linux.org.uk>2006-06-18 16:17:41 +0100
commitce7a3fdc5c55fd01d8e2deda0daef84473644f8b (patch)
treeb2aad3635d9026b0cf9c415cffc6345f0af05295
parent427abfa28afedffadfca9dd8b067eb6d36bac53f (diff)
downloadop-kernel-dev-ce7a3fdc5c55fd01d8e2deda0daef84473644f8b.zip
op-kernel-dev-ce7a3fdc5c55fd01d8e2deda0daef84473644f8b.tar.gz
[ARM] Remove rt_sigframe puc and pinfo pointers
These two members appear to be surplus to requirements. Discussing this issue with glibc folk: | > Additionally, do you see any need for these weird "puc" and "pinfo" | > pointers in the kernels rt_sigframe structure? Can we kill them? | | We can kill them. I checked with Phil B. about them last week, and he | didn't remember any reason they still needed to be there. And nothing | should know where they are on the stack. Unfortunately, doing this | will upset GDB, which knows that the saved registers are 0x88 bytes | above the stack pointer on entrance to an rt signal trampoline; but, | since puc and pinfo are quite recognizable, I can adapt GDB to support | the new layout if you want to remove them. So remove them. Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
-rw-r--r--arch/arm/kernel/signal.c4
1 files changed, 0 insertions, 4 deletions
diff --git a/arch/arm/kernel/signal.c b/arch/arm/kernel/signal.c
index a0cd0a9..0ddbf27 100644
--- a/arch/arm/kernel/signal.c
+++ b/arch/arm/kernel/signal.c
@@ -200,8 +200,6 @@ struct sigframe {
};
struct rt_sigframe {
- struct siginfo __user *pinfo;
- void __user *puc;
struct siginfo info;
struct ucontext uc;
unsigned long retcode[2];
@@ -511,8 +509,6 @@ setup_rt_frame(int usig, struct k_sigaction *ka, siginfo_t *info,
if (!frame)
return 1;
- __put_user_error(&frame->info, &frame->pinfo, err);
- __put_user_error(&frame->uc, &frame->puc, err);
err |= copy_siginfo_to_user(&frame->info, info);
__put_user_error(0, &frame->uc.uc_flags, err);
OpenPOWER on IntegriCloud