From: Micah Parrish <micah.parrish@hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: user-space unaligned accesses
Date: Sat, 11 Oct 2003 23:22:48 +0000 [thread overview]
Message-ID: <marc-linux-ia64-106608687732639@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-106562414203331@msgid-missing>
>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
I too see no reason to do a tty_write here. Most other error messages
of the same level (KERN_WARNING) do not do a tty_write, and syslogd can
be configured to write KERN_WARNING messages to the console or anywhere
else if you care. Smells like old debug code, and looks messy to the
end user.
-micah.parrish@hp.com
next prev parent reply other threads:[~2003-10-11 23:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-08 14:42 user-space unaligned accesses Bjorn Helgaas
2003-10-08 21:46 ` 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 [this message]
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-106608687732639@msgid-missing \
--to=micah.parrish@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox