From: Peter Waechtler <pwaechtler@mac.com>
To: Manfred Spraul <manfred@colorfullife.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] unified SysV and Posix mqueues as FS
Date: Mon, 28 Oct 2002 11:49:41 +0100 [thread overview]
Message-ID: <3DBD1645.518EFF07@mac.com> (raw)
In-Reply-To: <3DBCDF4A.3080709@colorfullife.com>
Manfred Spraul schrieb:
>
> Peter Waechtler wrote:
>
> >I plan to separate the interfaces and just share the message stuff.
> >But time was getting short. :)
> >
>
> Ok, you plan to rewrite the patch entirely, and what you have posted is
> a placeholder.
>
> How would the result look like?
> I'm thinking about
> - real syscalls
> - pipefs like filesystem stub, kern-only mounted, not visible for normal
> fs operations.
> - not using the sysv array
>
> Could you check the sus standard if that is permitted? A child would
> inherit the mqueue on fork().
>
Yes, I will check that - but I'm afraid of submitting too late.. :(
> For the locking stuff, the patch should probably depend on the sysv rcu
> patch, it cleans up locking a bit.
>
BTW, please have a look at ipc/util.c - the spinlock is held once
ipc_addid() is called and will deadlock when the array has to grow...
next prev parent reply other threads:[~2002-10-28 10:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-27 16:55 Manfred Spraul
2002-10-27 22:05 ` Peter Waechtler
[not found] ` <3DBCDF4A.3080709@colorfullife.com>
2002-10-28 10:49 ` Peter Waechtler [this message]
2002-10-28 21:39 ` Peter Waechtler
2002-10-28 21:43 ` Manfred Spraul
-- strict thread matches above, loose matches on Subject: below --
2002-10-27 15:33 Peter Waechtler
2002-10-27 15:47 ` Jeff Garzik
2002-10-27 15:53 ` Alexander Viro
2002-10-27 19:49 ` H. Peter Anvin
2002-10-27 22:02 ` Peter Waechtler
2002-10-28 1:54 ` Alexander Viro
2002-10-28 10:44 ` Peter Waechtler
2002-10-28 22:18 ` Bill Davidsen
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=3DBD1645.518EFF07@mac.com \
--to=pwaechtler@mac.com \
--cc=linux-kernel@vger.kernel.org \
--cc=manfred@colorfullife.com \
/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
Powered by JetHome