All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bjorn Helgaas <bjorn.helgaas@hp.com>
To: linux-ia64@vger.kernel.org
Subject: user-space unaligned accesses
Date: Wed, 08 Oct 2003 14:42:00 +0000	[thread overview]
Message-ID: <marc-linux-ia64-106562414203331@msgid-missing> (raw)

I got this from somebody at Red Hat.  Anybody want to comment on it?


-------------------------------------------------------
...
The ia64 architecture does a tty_write
on a userspace unaligned access. Not only is this extremenly annoying,
it's also very broken since the tty may well be suspended etc etc.
Doing a printk on such an access by default is very broken already,
lets not make it worse



--- linux/arch/ia64/kernel/unaligned.c~	2003-09-30 11:04:08.000000000 +0200
+++ linux/arch/ia64/kernel/unaligned.c	2003-09-30 11:04:08.000000000 +0200
@@ -1340,12 +1340,6 @@
 			len = sprintf(buf, "%s(%d): unaligned access to 0x%016lx, "
 				      "ip=0x%016lx\n\r", current->comm, current->pid,
 				      ifa, regs->cr_iip + ipsr->ri);
-			/*
-			 * Don't call tty_write_message() if we're in the kernel; we might
-			 * be holding locks...
-			 */
-			if (user_mode(regs))
-				tty_write_message(current->tty, buf);
 			buf[len-1] = '\0';	/* drop '\r' */
 			printk(KERN_WARNING "%s", buf);	/* watch for command names containing %s */
 		}





-------------------------------------------------------


             reply	other threads:[~2003-10-08 14:42 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-08 14:42 Bjorn Helgaas [this message]
2003-10-08 21:46 ` user-space unaligned accesses Grant Grundler
2003-10-08 22:54 ` Bjorn Helgaas
2003-10-08 23:36 ` David Mosberger
2003-10-09 13:53 ` Bjorn Helgaas
2003-10-11 23:22 ` Micah Parrish
2003-10-13 23:56 ` David Mosberger
2003-10-13 23:59 ` Duraid Madina

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-106562414203331@msgid-missing \
    --to=bjorn.helgaas@hp.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.