Re: [PATCH 0/4] cifs: pave way for change to "strictcache" by default

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, Apr 30, 2012 at 10:45 AM, Jeff Layton <jlayton@xxxxxxxxx> wrote:
> On Mon, 30 Apr 2012 10:11:43 -0500
> Steve French <smfrench@xxxxxxxxx> wrote:
>
>> There is a related question of how deferring writes slightly (e.g. to
>> buffer a full page or a full smb buffer) could corrupt data?
>>
>
> You're returning from write(2) without actually sending it to the
> backing store, but a read(2) will go to that backing store. So,
> applications that expect the results of that write to be visible to
> other clients (or even on the same client) won't see it.

well the results of the write MUST be visible to others reading
on the same client.  In what case would they not be
(other than perhaps some odd private memory mapping case)


-- 
Thanks,

Steve
--
To unsubscribe from this list: send the line "unsubscribe linux-cifs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux