From: Andi Kleen <ak@suse.de>
To: Dave Jones <davej@redhat.com>
Subject: Re: IA32 syscall 311 not implemented on x86_64
Date: Mon, 22 May 2006 00:37:57 +0200
User-Agent: KMail/1.9.1
Cc: Ulrich Drepper <drepper@gmail.com>, Chris Wedgwood <cw@f00f.org>,
       dragoran <dragoran@feuerpokemon.de>, linux-kernel@vger.kernel.org
References: <44702650.30507@feuerpokemon.de> <200605220019.08902.ak@suse.de> <20060521222831.GP8250@redhat.com>
In-Reply-To: <20060521222831.GP8250@redhat.com>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200605220037.58286.ak@suse.de>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1295
Lines: 35

On Monday 22 May 2006 00:28, Dave Jones wrote:
> On Mon, May 22, 2006 at 12:19:08AM +0200, Andi Kleen wrote:
> 
>  > >  > You make a good point.  In fact, given it's unthrottled, someone
>  > >  > with too much time on their hands could easily fill up a /var
>  > >  > just by calling unimplemented syscalls this way.
>  > 
>  > I never bought this argument because there are tons of printks in the kernel
>  > that can be triggered by everybody.
> 
> Then they should also be either rate limited, or removed.

Yes let's remove all that kernel debugging support. It is totally useless
for most users, isn't it?

Even if they are ratelimit you can still fill up /var.

> 
>  > > Actually it is kinda throttled, but only on process name.
>  > > This patch just removes that stuff completely.
>  > > (Also removes a bunch of trailing whitespace)
>  > 
>  > FF tree already has a different solution.
> 
> Adding a sysctl ? That seems way overkill to me.
> What practical purpose does that printk solve ?

Catching missing code in the compat layer.

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