lkml.org 
[lkml]   [2004]   [Apr]   [17]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: POSIX message queues, libmqueue: mq_open, mq_unlink
Chris Wright, Sat, Apr 17, 2004 01:56:21 +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.
>

Ok. It's just that every provider of the _kernel_ interface to user
space has now to take care of being posix-compliant. Write the code for
checks, iow. That is not the case for "open", for instance.
And besides, with the patch applied the kernel is also posix compliant,
isn't it? Noone still answered why the check in library in this case.
(The patch is not applied yet, btw)

-
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/

\
 
 \ /
  Last update: 2005-03-22 14:02    [from the cache]
©2003-2014 Jasper Spaans. Advertise on this site