From: Steve French <smfrench@gmail.com>
To: linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: Fwd: [PATCH 4/4] cifs: flush data on any setattr
Date: Thu, 26 Mar 2009 21:53:04 -0500 [thread overview]
Message-ID: <524f69650903261953u64744ed3i5280f137b02295@mail.gmail.com> (raw)
In-Reply-To: <524f69650903261952o6dd8497bnc8b10ae0a41721d4@mail.gmail.com>
---------- Forwarded message ----------
From: Steve French <smfrench@gmail.com>
Date: Thu, Mar 26, 2009 at 9:52 PM
Subject: Re: [PATCH 4/4] cifs: flush data on any setattr
To: Jeff Layton <jlayton@redhat.com>
Cc: linux-cifs-client@lists.samba.org
On Thu, Mar 26, 2009 at 12:35 PM, Jeff Layton <jlayton@redhat.com> wrote:
> We already flush all the dirty pages for an inode before doing
> ATTR_SIZE and ATTR_MTIME changes. There's another problem though -- if
> we change the mode so that the file becomes read-only then we may not
> be able to write data to it after a reconnect.
>
> Fix this by just going back to flushing all the dirty data on any
> setattr call.
> + * BB: This should be smarter. Why bother flushing pages that
> + * will be truncated anyway? Also, should we error out here if
> + * the flush returns error?
> + */
Merged the patch into cifs-2.6.git, but Jeff brings up an interesting
point about what really happens when we are shrinking the file size
(truncate) here ... is it possible that the vfs will flush pages that
are going to be thrown away
--
Thanks,
Steve
--
Thanks,
Steve
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
parent reply other threads:[~2009-03-27 2:53 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <524f69650903261952o6dd8497bnc8b10ae0a41721d4@mail.gmail.com>]
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=524f69650903261953u64744ed3i5280f137b02295@mail.gmail.com \
--to=smfrench@gmail.com \
--cc=linux-fsdevel@vger.kernel.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).