From: Liam Davies <ldavies@agile.tv>
To: linux-mips@oss.sgi.com
Cc: ralf@oss.sgi.com
Subject: [PATCH] mips_atomic_set fixups (with LLSC)
Date: Thu, 06 Dec 2001 15:43:54 +1000 [thread overview]
Message-ID: <3C0F059A.30709@agile.tv> (raw)
[-- Attachment #1: Type: text/plain, Size: 711 bytes --]
The kernel can be caused to crash when making the following syscall
sysmips(MIPS_ATOMIC_SET, [unaligned addr], value, 0);
The latest mips_atomic_set does not use the fixups that are defined
for the ll/sc instructions.
If an unaligned address is passed in we take the exception and
unaligned.c:emulate_load_store_insn ignores the fixups for the
ll/sc and sends a SIGBUS instead, thus causing the kernel to die.
The patch is to make the ll/sc instructions lookup the fixup table
and do them if present.
Also the fixup for the instructions in scall_o32.S appears to be
inappropriate, so the fixup is set to be bad_addr and an -EFAULT
is returned from the syscall.
Cheers
----
Liam Davies
ldavies@agile.tv
[-- Attachment #2: atomic_set.patch --]
[-- Type: text/plain, Size: 1292 bytes --]
--- ../sgi-cvs/arch/mips/kernel/unaligned.c Mon Dec 3 10:49:23 2001
+++ arch/mips/kernel/unaligned.c Thu Dec 6 15:07:00 2001
@@ -114,12 +114,14 @@
* These are instructions that a compiler doesn't generate. We
* can assume therefore that the code is MIPS-aware and
* really buggy. Emulating these instructions would break the
- * semantics anyway.
+ * semantics anyway. However, we do want to look at the exception
+ * table to see if we can exit gracefully.
*/
case ll_op:
case lld_op:
case sc_op:
case scd_op:
+ goto fault;
/*
* For these instructions the only way to create an address
--- ../sgi-cvs/arch/mips/kernel/scall_o32.S Mon Oct 8 09:56:02 2001
+++ arch/mips/kernel/scall_o32.S Thu Dec 6 15:34:47 2001
@@ -201,7 +201,7 @@
or a0, a0, a1
li v0, -EFAULT
and a0, a0, v1
- bltz a0, 8f
+ bltz a0, bad_address
#ifdef CONFIG_CPU_HAS_LLSC
/* Ok, this is the ll/sc case. World is sane :-) */
@@ -211,8 +211,8 @@
beqz a0, 1b
.section __ex_table,"a"
- PTR 1b, bad_stack
- PTR 2b, bad_stack
+ PTR 1b, bad_address
+ PTR 2b, bad_address
.previous
#else
sw a1, 16(sp)
@@ -256,8 +256,9 @@
no_mem: li v0, -ENOMEM
jr ra
-8: li v0, -EFAULT
-9: jr ra
+bad_address:
+ li v0, -EFAULT
+ jr ra
END(mips_atomic_set)
LEAF(sys_sysmips)
next reply other threads:[~2001-12-06 6:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-06 5:43 Liam Davies [this message]
2001-12-06 17:17 ` [PATCH] mips_atomic_set fixups (with LLSC) Ralf Baechle
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=3C0F059A.30709@agile.tv \
--to=ldavies@agile.tv \
--cc=linux-mips@oss.sgi.com \
--cc=ralf@oss.sgi.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