From: Christoph Rohland <hans-christoph.rohland@sap.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-mm@kvack.org, linux-kernel@vger.rutgers.edu,
ebiederm+eric@ccr.net, Alexander Viro <viro@math.psu.edu>
Subject: Re: [PATCH] get rid of vm_private_data and win posix shm
Date: 28 Dec 1999 19:38:28 +0100 [thread overview]
Message-ID: <qwwyaaegbbv.fsf@sap.com> (raw)
In-Reply-To: Alan Cox's message of "Tue, 28 Dec 1999 17:50:48 +0000 (GMT)"
Alan Cox <alan@lxorguk.ukuu.org.uk> writes:
> > I implemented posix shm with its own namespace by extending filp_open
> > and do_unlink by an additional parameter for the root inode.
> > Also extending this to a complete filesystem should be easy (but not
> > my target).
>
> It would seem that the best way to fix the inelegance of the patch - the
> shm_open and shm_unlink syscalls, the hacks on filp_open etc would be to do
> exactly that - make it a real fs, at least for open/unlink/openddir/readdir
> even if not for read/write
This makes the sysv ipc code dependent on a mounted fs. Also the
library has to know where this shm fs is mounted to implement shm_open
etc. I do not like these ideas. But I know this is questionable.
I will redo my patch to be much less intrusive into other code.
Greetings
Christoph
--
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.nl.linux.org/Linux-MM/
next prev parent reply other threads:[~1999-12-28 18:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-12-28 17:32 Christoph Rohland
1999-12-28 17:50 ` Alan Cox
1999-12-28 18:38 ` Christoph Rohland [this message]
[not found] ` <199912281914.LAA02201@penguin.transmeta.com>
1999-12-28 20:48 ` Christoph Rohland
1999-12-31 16:58 ` [PATCH] get rid of vm_private_data and win posix shm version 2 Christoph Rohland
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=qwwyaaegbbv.fsf@sap.com \
--to=hans-christoph.rohland@sap.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=ebiederm+eric@ccr.net \
--cc=linux-kernel@vger.rutgers.edu \
--cc=linux-mm@kvack.org \
--cc=viro@math.psu.edu \
/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