Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S964899AbWEUSuQ (ORCPT ); Sun, 21 May 2006 14:50:16 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S964907AbWEUSuQ (ORCPT ); Sun, 21 May 2006 14:50:16 -0400 Received: from mx1.redhat.com ([66.187.233.31]:36311 "EHLO mx1.redhat.com") by vger.kernel.org with ESMTP id S964899AbWEUSuP (ORCPT ); Sun, 21 May 2006 14:50:15 -0400 Date: Sun, 21 May 2006 14:50:00 -0400 From: Dave Jones To: Ulrich Drepper Cc: Chris Wedgwood , dragoran , linux-kernel@vger.kernel.org Subject: Re: IA32 syscall 311 not implemented on x86_64 Message-ID: <20060521185000.GB8250@redhat.com> Mail-Followup-To: Dave Jones , Ulrich Drepper , Chris Wedgwood , dragoran , linux-kernel@vger.kernel.org References: <44702650.30507@feuerpokemon.de> <20060521085015.GB2535@taniwha.stupidest.org> <20060521160332.GA8250@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1166 Lines: 26 On Sun, May 21, 2006 at 11:35:12AM -0700, Ulrich Drepper wrote: > On 5/21/06, Dave Jones wrote: > >It's a glibc problem really. > > It's not a glibc problem really. The problem is this stupid error > message in the kernel. We rely in many dozens of places on the kernel > returning ENOSYS in case a syscall is not implemented and we deal with > it appropriately. There is absolutely no justification to print these > messages except perhaps in debug kernels. IMO the sys32_ni_syscall > functions should just return ENOSYS unless you select a special debug > kernel. One doesn't need the kernel to detect missing syscall > implementations, strace can do this as well. 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. 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@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/