Re: IA32 syscall 311 not implemented on x86_64

[Dave Jones]

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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/