From: Ulrich Drepper <drepper@redhat.com>
To: Alex Riesen <fork0@users.sourceforge.net>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: POSIX message queues, libmqueue: mq_open, mq_unlink
Date: Fri, 16 Apr 2004 15:17:36 -0700 [thread overview]
Message-ID: <40805B80.30105@redhat.com> (raw)
In-Reply-To: <20040416213851.GA1784@steel.home>
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 ❖
next prev parent reply other threads:[~2004-04-16 22:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-16 8:11 POSIX message queues, libmqueue: mq_open, mq_unlink Alex Riesen
2004-04-16 16:13 ` Ulrich Drepper
2004-04-16 21:38 ` Alex Riesen
2004-04-16 22:17 ` Ulrich Drepper [this message]
2004-04-16 22:22 ` Chris Wright
2004-04-16 23:43 ` Alex Riesen
2004-04-16 23:56 ` Chris Wright
2004-04-17 8:20 ` Alex Riesen
-- strict thread matches above, loose matches on Subject: below --
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=40805B80.30105@redhat.com \
--to=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