All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Myers <bpm@sgi.com>
To: Brian Foster <bfoster@redhat.com>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH v4 0/2] fix spinlock recursion on xa_lock in xfs_buf_item_push
Date: Thu, 14 Feb 2013 17:32:05 -0600	[thread overview]
Message-ID: <20130214233205.GL22182@sgi.com> (raw)
In-Reply-To: <1360595302-15865-1-git-send-email-bfoster@redhat.com>

On Mon, Feb 11, 2013 at 10:08:20AM -0500, Brian Foster wrote:
> Hi all,
> 
> Here is v4 of the spinlock recursion fix. The only update is to the comment in
> patch 1. These changes have been run through the reproducer over the weekend
> without a failure.
> 
> I've also run another xfstests run while including the following patch from Dave:
> 
> xfs: xfs_bmap_add_attrfork_local is too generic
> 
> ... due to seeing the same issue Lukas reproduced in test 013 (I saw it in 070 as
> well). That problem no longer occurs with this patch included, but I have hit
> an error in test 178 that didn't fire in my baseline run. It persists if I revert
> back to TOT, so I'm posting this set as is and I'll see if I can trace where that
> one came from...

Applied these two.

Regards,
	Ben

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

      parent reply	other threads:[~2013-02-14 23:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-11 15:08 [PATCH v4 0/2] fix spinlock recursion on xa_lock in xfs_buf_item_push Brian Foster
2013-02-11 15:08 ` [PATCH v4 1/2] xfs: recheck buffer pinned status after push trylock failure Brian Foster
2013-02-11 21:53   ` Dave Chinner
2013-02-11 15:08 ` [PATCH v4 2/2] xfs: remove log force from xfs_buf_trylock() Brian Foster
2013-02-11 21:53   ` Dave Chinner
2013-02-14 23:32 ` Ben Myers [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=20130214233205.GL22182@sgi.com \
    --to=bpm@sgi.com \
    --cc=bfoster@redhat.com \
    --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.