From: xfs@oss.sgi.com
To: xfs@oss.sgi.com
Subject: [XFS updates] XFS development tree branch, xfs-fixes-for-3.18-rc3, updated. v3.18-rc2-5-g31692c5
Date: Wed, 29 Oct 2014 05:32:32 -0500 (CDT) [thread overview]
Message-ID: <20141029103232.BAE887F54@oss.sgi.com> (raw)
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "XFS development tree".
The branch, xfs-fixes-for-3.18-rc3 has been updated
31692c5 xfs: bulkstat needs to delete cursor at end of AG
from bae09893f6a5260c7030499ddfd0911899ae3d0c (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
commit 31692c5fe617d28d8099a9308d345e26f3e22dca
Author: Dave Chinner <david@fromorbit.com>
Date: Wed Oct 29 21:22:39 2014 +1100
xfs: bulkstat needs to delete cursor at end of AG
Colliding bug fixes meant one fix breaks from the bulkstat loop
("xfs: Check error during inode btree iteration in xfs_bulkstat()")
when in fact it should do what the other patch did introduced and
jump to the del_cursor label ("xfs: bulkstat doesn't release AGI
buffer on error").
Failure to do so causes the end of AG detection
to hang on a locked AGI.
Reported by: Tommy Wu <wu.tommy@gmail.com>
Signed-off-by: Dave Chinner <david@fromorbit.com>
-----------------------------------------------------------------------
Summary of changes:
fs/xfs/xfs_itable.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
hooks/post-receive
--
XFS development tree
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
reply other threads:[~2014-10-29 10:32 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20141029103232.BAE887F54@oss.sgi.com \
--to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox