From: John Ogness <dazukocode@ogness.net>
To: Pavel Machek <pavel@suse.cz>
Cc: linux-kernel@vger.kernel.org, viro@zeniv.linux.org.uk,
malware-list@lists.printk.net, eparis@redhat.com,
hch@infradead.org, alan@lxorguk.ukuu.org.uk
Subject: Re: [PATCH 0/5] VFS: DazukoFS, stackable-fs, file access control
Date: Wed, 24 Dec 2008 13:11:29 +0100 [thread overview]
Message-ID: <86d4fhwz66.fsf@johno-ibook.fn.ogness.net> (raw)
In-Reply-To: <20081224085300.GA1539@ucw.cz> (Pavel Machek's message of "Wed\, 24 Dec 2008 09\:53\:01 +0100")
On 2008-12-24, Pavel Machek <pavel@suse.cz> wrote:
>> If you are aware of a race condition in DazukoFS, please report
>> it. Thank you.
>
> I'm surprised, do you claim there is none?
It depends on how you want to define "race condition". DazukoFS (in
its current form) closes as many holes as default UNIX permissions or
SElinux. However, changing permissions (i.e. scanning files) _after_
two parties already have an open handle to the file is currently not
covered. But this issue is not unique to DazukoFS (although as a
stackable filesystem, DazukoFS could support this case as well).
> So how do you handle mmap(...MAP_SHARED) case?
DazukoFS currently does not support writing to memory mapped files for
this very reason. It needs to be determined how writing to memory
mapped files should be handled. I am choosing to tackle this issue
together with the Linux kernel community, rather than trying to solve
it within the much smaller Dazuko community.
Although memory mapped writing is currently not supported, I believe
DazukoFS still offers value to the Linux kernel. I am not aware of any
network services that require memory mapped writing for their sharing.
John Ogness
next prev parent reply other threads:[~2008-12-24 12:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-21 14:52 John Ogness
2008-12-21 14:56 ` [PATCH 1/5] " John Ogness
2008-12-21 14:57 ` [PATCH 2/5] " John Ogness
2008-12-21 14:59 ` [PATCH 3/5] " John Ogness
2008-12-21 15:00 ` [PATCH 4/5] " John Ogness
2008-12-21 15:01 ` [PATCH 5/5] " John Ogness
2008-12-21 15:48 ` [PATCH 1/5] " Bastian Blank
2008-12-21 17:56 ` John Ogness
2008-12-23 11:54 ` [PATCH 0/5] " Pavel Machek
2008-12-23 18:55 ` John Ogness
2008-12-24 8:53 ` Pavel Machek
2008-12-24 12:11 ` John Ogness [this message]
2008-12-26 18:30 ` Pavel Machek
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=86d4fhwz66.fsf@johno-ibook.fn.ogness.net \
--to=dazukocode@ogness.net \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=eparis@redhat.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=malware-list@lists.printk.net \
--cc=pavel@suse.cz \
--cc=viro@zeniv.linux.org.uk \
/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®