[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <86d4fhwz66.fsf@johno-ibook.fn.ogness.net>
Date: Wed, 24 Dec 2008 13:11:29 +0100
From: John Ogness <dazukocode@...ess.net>
To: Pavel Machek <pavel@...e.cz>
Cc: linux-kernel@...r.kernel.org, viro@...iv.linux.org.uk,
malware-list@...ts.printk.net, eparis@...hat.com,
hch@...radead.org, alan@...rguk.ukuu.org.uk
Subject: Re: [PATCH 0/5] VFS: DazukoFS, stackable-fs, file access control
On 2008-12-24, Pavel Machek <pavel@...e.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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists