Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S263901AbUDPWTb (ORCPT ); Fri, 16 Apr 2004 18:19:31 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S263887AbUDPWTT (ORCPT ); Fri, 16 Apr 2004 18:19:19 -0400 Received: from cpe-24-221-190-179.ca.sprintbbd.net ([24.221.190.179]:24536 "EHLO myware.akkadia.org") by vger.kernel.org with ESMTP id S263901AbUDPWR6 (ORCPT ); Fri, 16 Apr 2004 18:17:58 -0400 Message-ID: <40805B80.30105@redhat.com> Date: Fri, 16 Apr 2004 15:17:36 -0700 From: Ulrich Drepper Organization: Red Hat, Inc. User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7b) Gecko/20040411 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Alex Riesen CC: linux-kernel Subject: Re: POSIX message queues, libmqueue: mq_open, mq_unlink References: <20040416213851.GA1784@steel.home> In-Reply-To: <20040416213851.GA1784@steel.home> X-Enigmail-Version: 0.83.5.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 768 Lines: 18 Alex Riesen wrote: > And if the kernel code does check the incoming arguments correctly, > what is the point to check them again? Just to make the point, that > passing in not an absolute path is not portable? Forget what the kernel does. This is enforcement of the API the runtime provides. If must be stable regardless of what the kernel does. Including kernel changes which allow special names which do funky, non-standard things. -- ➧ Ulrich Drepper ➧ Red Hat, Inc. ➧ 444 Castro St ➧ Mountain View, CA ❖ - 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/