linux-kernel - Re: [V9fs-developer] [RFC PATCH -V2 0/17] Buffered write and writeable mmap support for 9P

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <AANLkTi=2XB+jK_fManbO93TEbZ2=r51YR_HpWpTt8Mcx@mail.gmail.com>
Date:	Mon, 7 Feb 2011 08:58:06 -0600
From:	Eric Van Hensbergen <ericvh@...il.com>
To:	"Aneesh Kumar K. V" <aneesh.kumar@...ux.vnet.ibm.com>
Cc:	v9fs-developer@...ts.sourceforge.net,
	linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [V9fs-developer] [RFC PATCH -V2 0/17] Buffered write and
 writeable mmap support for 9P

On Sat, Feb 5, 2011 at 12:03 PM, Aneesh Kumar K. V
<aneesh.kumar@...ux.vnet.ibm.com> wrote:
> On Sat,  5 Feb 2011 23:16:28 +0530, "Aneesh Kumar K.V" <aneesh.kumar@...ux.vnet.ibm.com> wrote:
>> The patch series implement buffered write and writeable mmap for 9P
>>
>> Changes from V1:
>> a) Add fsync and syncfs support
>>
>
> I haven't yet addressed the previous review feedback from
> Miklos. http://article.gmane.org/gmane.linux.kernel/1093869
> Running 9p server and client on the same host even though possible
> is not a strong use case at this point. I will get to that later.
>

It is for a lot of the legacy cases including using 9p to access
user-space file servers.  Of course, there are some long standing
issues with this for anything which re-exports the name space.  Also -
most user-space file servers on the same host wouldn't want cache
support anyways.

>
> The patch series also don't address cache consistency issue that
> can arise due to direct modification in the server. I am not
> sure we need to complicate the client code for that considering
> the cache model that we follow is loose.
>

Agreed, the loose cache model doesn't respect any consistency
guarantees.  Once we implement any of the more conventional cache
policies we'll have to worry about it.

       -eric
--
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/