Date: Fri, 16 Apr 2004 16:56:21 -0700
From: Chris Wright <chrisw@osdl.org>
To: Alex Riesen <fork0@users.sourceforge.net>, Chris Wright <chrisw@osdl.org>,
       Ulrich Drepper <drepper@redhat.com>,
       linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: POSIX message queues, libmqueue: mq_open, mq_unlink
Message-ID: <20040416165621.V21045@build.pdx.osdl.net>
References: <4080060F.7030604@redhat.com> <20040416213851.GA1784@steel.home> <20040416152217.C22989@build.pdx.osdl.net> <20040416234303.GA1932@steel.home>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <20040416234303.GA1932@steel.home>; from fork0@users.sourceforge.net on Sat, Apr 17, 2004 at 01:43:03AM +0200
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1154
Lines: 28

* Alex Riesen (fork0@users.sourceforge.net) wrote:
> Chris Wright, Sat, Apr 17, 2004 00:22:17 +0200:
> > The kernel interface is simple and clean.  And in fact, requires no
> > slashes else you'll get -EACCES.  It's not POSIX, but the library
> > interface is.
> > 
> > We just discussed this yesterday:
> > 
> > http://marc.theaimsgroup.com/?t=108205593100003&r=1&w=2
> 
> now, what's is the check in the library for? BTW, it is returning the
> other error code (EINVAL instead of EACCES), just on top of all the
> confusion with slashes.

EINVAL in the library, sure.  EACCES is if you directly use the kernel
interface and pass it a name with any slashes in it.  The two interfaces
(library and kernel) aren't required to be identical.  Kernel is kept
simplest w/ no slashes, library provides POSIX compliance.

thanks,
-chris
-- 
Linux Security Modules     http://lsm.immunix.org     http://lsm.bkbits.net
-
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/