From: Bob Peterson <rpeterso@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [GFS2 PATCH 0/5] gfs2; jdata io deadlocks
Date: Thu, 26 Mar 2020 13:40:15 -0500 [thread overview]
Message-ID: <20200326184020.123544-1-rpeterso@redhat.com> (raw)
This patch set addresses several problems I encountered while testing writes
to journaled data (jdata) files.
Bob Peterson (5):
gfs2: don't lock sd_log_flush_lock in try_rgrp_unlink
gfs2: instrumentation wrt ail1 stuck
gfs2: change from write to read lock for sd_log_flush_lock in journal
replay
gfs2: special log flush sequence to protect jdata writes
gfs2: implement special transaction type for jdata sync writes
fs/gfs2/aops.c | 25 ++++++--
fs/gfs2/glops.c | 2 +-
fs/gfs2/incore.h | 1 +
fs/gfs2/log.c | 137 +++++++++++++++++++++++++++++++++----------
fs/gfs2/log.h | 6 +-
fs/gfs2/ops_fstype.c | 1 +
fs/gfs2/recovery.c | 4 +-
fs/gfs2/rgrp.c | 2 -
fs/gfs2/trans.c | 39 +++++++++---
fs/gfs2/trans.h | 4 ++
10 files changed, 171 insertions(+), 50 deletions(-)
--
2.25.1
next reply other threads:[~2020-03-26 18:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-26 18:40 Bob Peterson [this message]
2020-03-26 18:40 ` [Cluster-devel] [GFS2 PATCH 1/5] gfs2: don't lock sd_log_flush_lock in try_rgrp_unlink Bob Peterson
2020-03-26 18:40 ` [Cluster-devel] [GFS2 PATCH 2/5] gfs2: instrumentation wrt ail1 stuck Bob Peterson
2020-03-26 18:40 ` [Cluster-devel] [GFS2 PATCH 3/5] gfs2: change from write to read lock for sd_log_flush_lock in journal replay Bob Peterson
2020-03-26 18:40 ` [Cluster-devel] [GFS2 PATCH 4/5] gfs2: special log flush sequence to protect jdata writes Bob Peterson
2020-03-27 21:38 ` Andreas Gruenbacher
2020-03-26 18:40 ` [Cluster-devel] [GFS2 PATCH 5/5] gfs2: implement special transaction type for jdata sync writes Bob Peterson
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=20200326184020.123544-1-rpeterso@redhat.com \
--to=rpeterso@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).