From: Keith Owens <kaos@ocs.com.au>
To: linux-ia64@vger.kernel.org
Subject: [Linux-ia64] [patch] 2.4.20-ia64-021210 prevent loop on zero instruction
Date: Wed, 11 Dec 2002 12:48:15 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590709805543@msgid-missing> (raw)
On Tue, 10 Dec 2002 21:44:12 -0700,
Bjorn Helgaas <bjorn_helgaas@hp.com> wrote:
>The latest ia64 kernel patch for Linux 2.4.20 is available here:
>
> ftp://ftp.kernel.org/pub/linux/kernel/ports/ia64/v2.4/linux-2.4.20-ia64-021210.diff.gz
Trivial backport of a fix from 2.5 ia64. Prevents the kernel looping
on a zero instruction.
--- arch/ia64/kernel/traps.c.orig Wed Dec 11 23:44:14 2002
+++ arch/ia64/kernel/traps.c Wed Dec 11 23:45:47 2002
@@ -143,6 +143,7 @@
switch (break_num) {
case 0: /* unknown error */
+ die_if_kernel("bad break", regs, break_num);
sig = SIGILL; code = ILL_ILLOPC;
break;
next reply other threads:[~2002-12-11 12:48 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-11 12:48 Keith Owens [this message]
2003-03-14 4:39 ` [Linux-ia64] [patch] 2.4.20-ia64-021210 unwind.c - allow unw_access_gr(r0) Keith Owens
2003-03-15 0:01 ` Bjorn Helgaas
2003-03-15 1:10 ` [Linux-ia64] [patch] 2.4.20-ia64-021210 new spinlock code Keith Owens
2003-03-15 1:30 ` David Mosberger
2003-03-15 2:36 ` Keith Owens
2003-03-15 2:40 ` Keith Owens
2003-03-15 6:46 ` David Mosberger
2003-03-15 10:31 ` Keith Owens
2003-03-27 20:29 ` David Mosberger
2003-03-27 23:15 ` Keith Owens
2003-03-27 23:32 ` David Mosberger
2003-03-28 1:39 ` Keith Owens
2003-03-28 1:45 ` David Mosberger
2003-03-28 1:49 ` Keith Owens
2003-03-28 1:53 ` David Mosberger
2003-03-28 2:10 ` Keith Owens
2003-03-28 2:14 ` David Mosberger
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=marc-linux-ia64-105590709805543@msgid-missing \
--to=kaos@ocs.com.au \
--cc=linux-ia64@vger.kernel.org \
/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