linux-xfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: sandeen@redhat.com, darrick.wong@oracle.com
Cc: linux-xfs@vger.kernel.org
Subject: [PATCH 0/4] xfsprogs-4.17: tooling fixes
Date: Tue, 08 May 2018 09:37:14 -0700	[thread overview]
Message-ID: <152579743411.10641.4577883761846454290.stgit@magnolia> (raw)

Hi all,

The first three patches of this series fix some deficiencies I found
when I tried to use xfsbuflock.py to diagnose deadlocks in generic/388.
The script didn't know that buffers are created locked, it didn't tell
you the line number of when a buffer got locked, and it got a little
confused about trylock.  So fix all three of those.

The fourth patch fixes another bashism in fsck.xfs.

This probably won't eat your data, and the branch[2] should apply
against for-next.

--D

[1] https://git.kernel.org/cgit/linux/kernel/git/djwong/xfsprogs-dev.git/log/?h=djwong-devel

             reply	other threads:[~2018-05-08 16:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-08 16:37 Darrick J. Wong [this message]
2018-05-08 16:37 ` [PATCH 1/4] xfs_buflock: ignore if buffer already locked Darrick J. Wong
2018-05-08 16:37 ` [PATCH 2/4] xfs_buflock: record line number of trace where we locked the buffer Darrick J. Wong
2018-05-08 16:37 ` [PATCH 3/4] xfs_buflock: record buffer initialization Darrick J. Wong
2018-05-08 16:37 ` [PATCH 4/4] fsck: fix more bashisms Darrick J. Wong
2018-05-08 16:47   ` Eric Sandeen
2018-05-14 23:42 ` [PATCH 5/4] xfs_scrub: actually check for errors coming from close() Darrick J. Wong

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=152579743411.10641.4577883761846454290.stgit@magnolia \
    --to=darrick.wong@oracle.com \
    --cc=linux-xfs@vger.kernel.org \
    --cc=sandeen@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 NNTP newsgroup(s).