From: Richard Hirst <rhirst@linuxcare.com>
To: parisc-linux@thepuffingroup.com
Subject: [parisc-linux] parisc64 kernel and ret1 (gr29) setup
Date: Thu, 21 Dec 2000 16:00:06 +0000 [thread overview]
Message-ID: <20001221160006.W2554@linuxcare.com> (raw)
Hi,
I tried calling ptrace() from a 32 bit app on a 64 bit kernel, and
the kernel crashed. sys_ptrace needs a 32 bit wrapper, but that is
a seperate issue (I think).
It died at sys_ptrace+0x28, where it tried to use ret1.
(ret1 = 00000000000517a1):
0000000000000000 <sys_ptrace>:
0: 0f c2 12 c1 std rp,-10(sr0,sp)
4: 37 de 03 00 ldo 180(sp),sp
8: 73 c5 3e 51 std r5,-d8(sp)
c: 37 a5 3f 81 ldo -40(ret1),r5
10: 73 c4 3e 61 std r4,-d0(sp)
14: 08 1b 02 44 copy dp,r4
18: db 39 0f e0 extrd,s r25,63,32,r25
1c: 73 c8 3e 31 std r8,-e8(sp)
20: 73 c6 3e 41 std r6,-e0(sp)
24: 73 c3 3e 71 std r3,-c8(sp)
28: 73 b7 3f b1 std r23,-28(ret1)
2c: ef 40 2e 28 cmpib,*= 0,r26,748 <.L1098+0x7c>
30: 34 08 3f ff ldi -1,r8
34: d3 33 1e e8 extrw,s r25,23,24,r19
38: 2b 60 00 00 addil 0,dp,%r1
38: R_PARISC_DLTIND21L pidhash
At the moment we set up sp with "ldo TASK_SZ_ALGN+64(%r1),%r30" on syscall
entry. For 64 bit presumably we should do something like:
ldo TASK_SZ_ALGN+80(%r1),%r30
ldo -16(%r30),%r29
Which gives 64 bytes for parameter saves, plus 16 bytes for rp+sp, and
initialises ret1.
Does that sound right?
Richard
next reply other threads:[~2000-12-21 16:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-21 16:00 Richard Hirst [this message]
2000-12-21 20:57 ` [parisc-linux] parisc64 kernel and ret1 (gr29) setup Matthew Wilcox
2000-12-21 20:55 ` Richard Hirst
2001-01-23 13:45 ` Richard Hirst
2001-01-23 14:20 ` Alan Modra
2001-01-23 14:30 ` Matthew Wilcox
2001-01-23 15:43 ` Richard Hirst
2001-02-07 11:18 ` Richard Hirst
2001-02-11 12:09 ` Alan Modra
2001-02-11 23:03 ` Richard Hirst
-- strict thread matches above, loose matches on Subject: below --
2001-01-23 18:47 Cary Coutant
2001-01-23 21:17 ` Jeffrey A Law
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20001221160006.W2554@linuxcare.com \
--to=rhirst@linuxcare.com \
--cc=parisc-linux@thepuffingroup.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox