From: Dave Jones <davej@redhat.com>
To: dragoran <dragoran@feuerpokemon.de>
Cc: Andi Kleen <ak@suse.de>, Ulrich Drepper <drepper@gmail.com>,
Chris Wedgwood <cw@f00f.org>,
linux-kernel@vger.kernel.org
Subject: Re: IA32 syscall 311 not implemented on x86_64
Date: Mon, 22 May 2006 08:41:02 -0400 [thread overview]
Message-ID: <20060522124102.GB3486@redhat.com> (raw)
In-Reply-To: <4471533C.2030605@feuerpokemon.de>
On Mon, May 22, 2006 at 07:59:24AM +0200, dragoran wrote:
> >If a regular user can trip up debugging printks, yes, lets remove it.
> >Examples ?
> >
> allmost all selinux messages.
I assume you mean AVC messages ? They indicate something that should be
fixed in selinux policy (or that your filesystem is incorrectly labelled
-- such as if you've booted with selinux=0 at any point).
They can also get filtered with the audit subsystem to /var/log/audit/, never
hitting the dmesg ringbuffer.
Dave
--
http://www.codemonkey.org.uk
next prev parent reply other threads:[~2006-05-22 12:41 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-21 8:35 IA32 syscall 311 not implemented on x86_64 dragoran
2006-05-21 8:50 ` Chris Wedgwood
2006-05-21 9:06 ` dragoran
2006-05-21 9:11 ` Chris Wedgwood
2006-05-21 9:26 ` dragoran
2006-05-21 9:54 ` dragoran
2006-05-21 16:03 ` Dave Jones
2006-05-21 18:35 ` Ulrich Drepper
2006-05-21 18:50 ` Dave Jones
2006-05-21 18:56 ` Dave Jones
2006-05-21 19:38 ` Adrian Bunk
2006-05-21 19:47 ` Dave Jones
2006-05-22 0:17 ` [2.6 patch] x86_64: don't printk for unimplemented 32bit syscalls Adrian Bunk
2006-05-21 22:19 ` IA32 syscall 311 not implemented on x86_64 Andi Kleen
2006-05-21 22:28 ` Dave Jones
2006-05-21 22:37 ` Andi Kleen
2006-05-21 23:48 ` Dave Jones
2006-05-21 23:51 ` Chris Wedgwood
2006-05-22 5:59 ` dragoran
2006-05-22 12:41 ` Dave Jones [this message]
2006-05-23 14:30 ` Denis Vlasenko
2006-05-21 23:09 ` Andrew Morton
2006-05-21 19:35 ` Chris Wedgwood
2006-05-21 19:38 ` Dave Jones
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=20060522124102.GB3486@redhat.com \
--to=davej@redhat.com \
--cc=ak@suse.de \
--cc=cw@f00f.org \
--cc=dragoran@feuerpokemon.de \
--cc=drepper@gmail.com \
--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