All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Kleikamp <dave.kleikamp@oracle.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: jfs-discussion@lists.sourceforge.net, xfs@oss.sgi.com
Subject: Re: [PATCH] jfs: flush journal completely before releasing metadata inodes
Date: Mon, 01 Aug 2011 15:04:32 -0500	[thread overview]
Message-ID: <4E3706D0.1000304@oracle.com> (raw)
In-Reply-To: <20110801183255.GA30985@infradead.org>



On 08/01/2011 01:32 PM, Christoph Hellwig wrote:
> On Mon, Aug 01, 2011 at 01:29:26PM -0500, Dave Kleikamp wrote:
>> On 07/29/2011 11:03 AM, Dave Kleikamp wrote:

>> This fixes a race during unmount. We need to not only make sure that
>> the journal is completely written, but that the metadata changes make
>> it to disk before releasing ipimap and ipbmap.
> 
> Looks sensible.  How far does a ./check -g auto get now?  Any other
> failures?

It runs through them all. A lot of tests get skipped claiming not to be
supported on jfs. A failure because jfs doesn't support fallocate and
hole-punch, but no crashes.

Shaggy

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2011-08-01 20:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-29 15:50 [PATCH, RFC] jfs support for xfstests Christoph Hellwig
2011-07-29 16:03 ` [Jfs-discussion] " Dave Kleikamp
2011-08-01 18:29   ` [PATCH] jfs: flush journal completely before releasing metadata inodes Dave Kleikamp
2011-08-01 18:32     ` Christoph Hellwig
2011-08-01 20:04       ` Dave Kleikamp [this message]
2011-08-02 10:25         ` Christoph Hellwig

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=4E3706D0.1000304@oracle.com \
    --to=dave.kleikamp@oracle.com \
    --cc=hch@infradead.org \
    --cc=jfs-discussion@lists.sourceforge.net \
    --cc=xfs@oss.sgi.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.