From: Steve French <smfrench-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Jeff Layton <jlayton-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-fsdevel
<linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH 3/3] cifs: don't allow mmap'ed pages to be dirtied while under writeback
Date: Sun, 27 Mar 2011 10:00:12 -0500 [thread overview]
Message-ID: <AANLkTin3wa-b188+8FU1coKbnv0WpDNc_XuaYLQ952s3@mail.gmail.com> (raw)
In-Reply-To: <20110327073204.3e85ad65-9yPaYZwiELC+kQycOl6kW4xkIHaj4LzF@public.gmane.org>
I like this patch very much, but had been waiting for any
comments/ack/reviewed-by
one of those more familiar with this part of the mm layer.
Barring any objections, I plan to merge this (and the performance fix)
after some additional review today or tomorrow.
On Sun, Mar 27, 2011 at 6:32 AM, Jeff Layton <jlayton-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org> wrote:
> On Wed, 16 Mar 2011 15:15:31 -0400
> Jeff Layton <jlayton-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org> wrote:
>
>> If a process has a dirty page mapped into its page tables, then it has
>> the ability to change it while the client is trying to write the data
>> out to the server. If that happens after the signature has been
>> calculated then that signature will then be wrong, and the server will
>> likely reset the TCP connection.
>>
>> This patch adds a page_mkwrite handler for CIFS that simply takes the
>> page lock. Because the page lock is held over the life of writepage and
>> writepages, this prevents the page from becoming writeable until
>> the write call has completed.
>>
>> With this, we can also remove the "sign_zero_copy" module option and
>> always inline the pages when writing.
>>
>> Signed-off-by: Jeff Layton <jlayton-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
>> ---
>> fs/cifs/cifsfs.c | 4 ---
>> fs/cifs/cifsglob.h | 1 -
>> fs/cifs/file.c | 62 ++++++++++++++++++++++++++--------------------------
>> 3 files changed, 31 insertions(+), 36 deletions(-)
>>
>
> Steve, can you let me know where we are with this patch? It's not
> merged and you haven't commented on it.
>
> --
> Jeff Layton <jlayton-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
>
--
Thanks,
Steve
parent reply other threads:[~2011-03-27 15:00 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20110327073204.3e85ad65-9yPaYZwiELC+kQycOl6kW4xkIHaj4LzF@public.gmane.org>]
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=AANLkTin3wa-b188+8FU1coKbnv0WpDNc_XuaYLQ952s3@mail.gmail.com \
--to=smfrench-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=jlayton-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
/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;
as well as URLs for NNTP newsgroup(s).