From: Tavis Ormandy <taviso@gentoo.org>
To: Ivan Kokshaysky <ink@jurassic.park.msu.ru>
Cc: linux-kernel@vger.kernel.org, alpha@gentoo.org
Subject: Re: [PATCH] 2.4.21: Optionally Configure UAC Policy via Sysctl (Alpha)
Date: Thu, 10 Jul 2003 11:50:01 +0000 [thread overview]
Message-ID: <20030710115001.GA997@sdf.lonestar.org> (raw)
In-Reply-To: <20030710153217.A21944@jurassic.park.msu.ru>
On Thu, Jul 10, 2003 at 03:32:17PM +0400, Ivan Kokshaysky wrote:
> On Thu, Jul 10, 2003 at 08:15:13AM +0000, Tavis Ormandy wrote:
> > + To disable the warning messages at runtime, you might use
> > +
> > + echo 1 > /proc/sys/kernel/uac/noprint
>
> It's really bad idea. Unaligned traps are *bugs*, so we don't
> want to hide them. Especially system-wide.
>
It's true that that they are bugs, but on such widespread errors that
are transparently fixed by the kernel, do we really need to be reminded
every time such an event occurs?
$ grep unaligned /proc/cpuinfo
kernel unaligned acc : 0 (pc=0,va=0)
user unaligned acc : 4400 (pc=30281c8c434,va=30281db8f62)
This machine has been up just a few hours, and already a has fixed a lot
of these errors. I really dont need the signal:noise ratio of my logs
diluted by this, unless im searching for bugs, which is why a sysctl
makes sense, imo.
> You can do all the same per process, using existing OSF-compatible
> UAC control.
>
True, and thats _really_ useful for turning the messages _on_ for the
application your working with/debugging/etc, system-wide messages just
dont make sense to me.
Also, it is optional, so only users who foresee wanting to disable the
messages will do so.
--
-------------------------------------
taviso@sdf.lonestar.org | finger me for my gpg key.
-------------------------------------------------------
prev parent reply other threads:[~2003-07-10 11:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-10 8:15 Tavis Ormandy
2003-07-10 11:32 ` Ivan Kokshaysky
2003-07-10 11:50 ` Tavis Ormandy [this message]
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=20030710115001.GA997@sdf.lonestar.org \
--to=taviso@gentoo.org \
--cc=alpha@gentoo.org \
--cc=ink@jurassic.park.msu.ru \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®