public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ben Pfaff <blp@cs.stanford.edu>
To: Dave Kleikamp <shaggy@austin.ibm.com>
Cc: JFS Discussion <jfs-discussion@lists.sourceforge.net>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	mc@cs.stanford.edu
Subject: Re: [CHECKER] writes not always synchronous on JFS with O_SYNC?
Date: Tue, 22 Mar 2005 11:47:42 -0800	[thread overview]
Message-ID: <87u0n331k1.fsf@benpfaff.org> (raw)
In-Reply-To: <1111520471.8082.9.camel@localhost> (Dave Kleikamp's message of "Tue, 22 Mar 2005 13:41:11 -0600")

Dave Kleikamp <shaggy@austin.ibm.com> writes:

> This patch to jfs_fsck fixes the problem.  It wasn't really an issue
> with O_SYNC at all, although I believe there are O_SYNC issues that need
> to be resolved.  The data itself should be sync'd correctly, as
> generic_file_write checks for the O_SYNC flag.  The missing piece in jfs
> is that metadata changes to the inode may not always be making it to the
> disk when they should.

Wow, that's an amazingly fast fix.  Thanks!  If I have time
today, I'll re-run the checker after applying your patch.
-- 
Ben Pfaff 
email: blp@cs.stanford.edu
web: http://benpfaff.org

      reply	other threads:[~2005-03-22 19:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-21 21:10 [CHECKER] writes not always synchronous on JFS with O_SYNC? Ben Pfaff
2005-03-22 13:43 ` Dave Kleikamp
2005-03-22 19:41   ` Dave Kleikamp
2005-03-22 19:47     ` Ben Pfaff [this message]

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=87u0n331k1.fsf@benpfaff.org \
    --to=blp@cs.stanford.edu \
    --cc=jfs-discussion@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mc@cs.stanford.edu \
    --cc=shaggy@austin.ibm.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