public inbox for cluster-cvs@sourceware.org
help / color / mirror / Atom feed
From: bmarzins@sourceware.org
To: cluster-cvs@sources.redhat.com
Subject: cluster/gfs-kernel/src/gfs ops_file.c
Date: Sat, 10 Dec 2005 00:44:00 -0000	[thread overview]
Message-ID: <20051210004412.16677.qmail@sourceware.org> (raw)

CVSROOT:	/cvs/cluster
Module name:	cluster
Changes by:	bmarzins@sourceware.org	2005-12-10 00:44:12

Modified files:
	gfs-kernel/src/gfs: ops_file.c 

Log message:
	Fix for bz 142849
	
	When you do gfs_write on a stuffed inode, you don't update the page cache,
	because the inodes are stored in the buffer cache. This doesn't effect reads,
	because gfs special cases the stuffed reads.  Unfortunately, sendfile needs to
	use the page cache, because it relys on the destination socket's sendpage
	routine to work. So my fix is: after you do a write on a stuffed inode, if the
	first page of the file is cached (It appears from looking at the code that
	there is already an assumption that stuffed inodes will never be more than a
	page in length) mark the cached page as not uptodate.

Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/cluster/gfs-kernel/src/gfs/ops_file.c.diff?cvsroot=cluster&r1=1.20&r2=1.21


             reply	other threads:[~2005-12-10  0:44 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-10  0:44 bmarzins [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-01-30  9:05 fabbione
2008-01-28  6:36 fabbione
2007-06-17  3:35 wcheng
2007-06-17  2:56 wcheng
2007-05-24 22:34 wcheng
2007-05-04 14:49 wcheng
2007-01-17 22:30 wcheng
2006-11-17 20:39 wcheng
2006-11-17 20:33 wcheng
2006-11-17 20:26 wcheng
2006-11-17 19:49 wcheng
2006-11-17 16:15 wcheng
2006-11-17  5:00 wcheng
2006-10-27 16:22 wcheng
2006-10-24  3:35 wcheng
2006-06-07 14:06 wcheng
2006-06-02  4:56 wcheng
2006-05-31 18:29 wcheng
2006-05-23 22:28 wcheng
2006-05-13  2:51 wcheng
2006-02-13 20:28 cfeist
2006-01-05 17:18 teigland
2005-12-10  0:48 bmarzins
2005-12-10  0:47 bmarzins
2005-12-10  0:44 bmarzins
2005-11-21 16:51 teigland
2005-11-21 16:49 teigland
2005-11-21 16:41 teigland
2005-11-17 20:21 wcheng
2005-11-14 22:52 wcheng
2005-11-01 19:23 wcheng

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=20051210004412.16677.qmail@sourceware.org \
    --to=bmarzins@sourceware.org \
    --cc=cluster-cvs@sources.redhat.com \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).