mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Chris Wright <chrisw@osdl.org>
To: Alex Riesen <fork0@users.sourceforge.net>,
	Ulrich Drepper <drepper@redhat.com>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: POSIX message queues, libmqueue: mq_open, mq_unlink
Date: Fri, 16 Apr 2004 15:22:17 -0700	[thread overview]
Message-ID: <20040416152217.C22989@build.pdx.osdl.net> (raw)
In-Reply-To: <20040416213851.GA1784@steel.home>; from fork0@users.sourceforge.net on Fri, Apr 16, 2004 at 11:38:51PM +0200

* Alex Riesen (fork0@users.sourceforge.net) wrote:
> My concern is that the tests are rather pointing that something in
> kernel is not implemented correctly. _The_ checks in particular.
> Because if they _are_ implemented correctly, you don't need to patch the
> functionality in the user space.
>
> 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?

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

thanks,
-chris
-- 
Linux Security Modules     http://lsm.immunix.org     http://lsm.bkbits.net

  parent reply	other threads:[~2004-04-16 22:25 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-16  8:11 Alex Riesen
2004-04-16 16:13 ` Ulrich Drepper
2004-04-16 21:38   ` Alex Riesen
2004-04-16 22:17     ` Ulrich Drepper
2004-04-16 22:22     ` Chris Wright [this message]
2004-04-16 23:43       ` Alex Riesen
2004-04-16 23:56         ` Chris Wright
2004-04-17  8:20           ` Alex Riesen
2004-04-17 10:49 Manfred Spraul
2004-04-17 11:16 ` Alex Riesen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20040416152217.C22989@build.pdx.osdl.net \
    --to=chrisw@osdl.org \
    --cc=drepper@redhat.com \
    --cc=fork0@users.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®