From: Bob Peterson <rpeterso@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [GFS2 PATCH 00/11] gfs2: jdata patch collection
Date: Fri, 24 Jul 2020 13:32:53 -0500 [thread overview]
Message-ID: <20200724183304.366913-1-rpeterso@redhat.com> (raw)
These patches are for the jdata problems I've recently found. They allow
xfstests to pass in its entirety using jdata, and unlike before, 269
can be run multiple times without deadlocking. The last two patches are
just improvements to the log_blocks kernel trace point, which can be
pushed (or not) separately.
Bob Peterson (11):
gfs2: inline gfs2_write_jdata_pagevec into gfs2_write_cache_jdata
gfs2: don't break integrity writeback on __gfs2_jdata_writepage error
gfs2: Fix inaccurate comment
gfs2: don't try to add buffers to transactions a second time for jdata
gfs2: Wipe jdata and ail1 in gfs2_journal_wipe, formerly
gfs2_meta_wipe
gfs2: rename gfs2_write_full_page to gfs2_write_jdata_page, remove
parm
gfs2: Add a new jdata-specific version of gfs2_get_block_noalloc
gfs2: Add caller info to log_blocks trace point
gfs2: enhance log_blocks trace point to show log blocks free
gfs2: print details on transactions that aren't properly ended
gfs2: Never call gfs2_block_zero_range with an open transaction
fs/gfs2/aops.c | 267 +++++++++++++++++++++++--------------------
fs/gfs2/bmap.c | 70 +++++++-----
fs/gfs2/incore.h | 3 +
fs/gfs2/log.c | 26 +++--
fs/gfs2/lops.c | 1 +
fs/gfs2/meta_io.c | 82 ++++++++++++-
fs/gfs2/meta_io.h | 5 +-
fs/gfs2/ops_fstype.c | 2 +-
fs/gfs2/rgrp.c | 6 +-
fs/gfs2/trace_gfs2.h | 23 +++-
fs/gfs2/trans.c | 31 ++---
11 files changed, 327 insertions(+), 189 deletions(-)
--
2.26.2
next reply other threads:[~2020-07-24 18:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-24 18:32 Bob Peterson [this message]
2020-07-24 18:32 ` [Cluster-devel] [GFS2 PATCH 01/11] gfs2: inline gfs2_write_jdata_pagevec into gfs2_write_cache_jdata Bob Peterson
2020-07-24 18:32 ` [Cluster-devel] [GFS2 PATCH 02/11] gfs2: don't break integrity writeback on __gfs2_jdata_writepage error Bob Peterson
2020-08-03 17:54 ` Andreas Gruenbacher
2020-07-24 18:32 ` [Cluster-devel] [GFS2 PATCH 03/11] gfs2: Fix inaccurate comment Bob Peterson
2020-07-24 18:32 ` [Cluster-devel] [GFS2 PATCH 04/11] gfs2: don't try to add buffers to transactions a second time for jdata Bob Peterson
2020-08-03 17:52 ` Andreas Gruenbacher
2020-07-24 18:32 ` [Cluster-devel] [GFS2 PATCH 05/11] gfs2: Wipe jdata and ail1 in gfs2_journal_wipe, formerly gfs2_meta_wipe Bob Peterson
2020-07-24 18:32 ` [Cluster-devel] [GFS2 PATCH 06/11] gfs2: rename gfs2_write_full_page to gfs2_write_jdata_page, remove parm Bob Peterson
2020-07-24 18:33 ` [Cluster-devel] [GFS2 PATCH 07/11] gfs2: Add a new jdata-specific version of gfs2_get_block_noalloc Bob Peterson
2020-07-24 18:33 ` [Cluster-devel] [GFS2 PATCH 08/11] gfs2: Add caller info to log_blocks trace point Bob Peterson
2020-07-24 18:33 ` [Cluster-devel] [GFS2 PATCH 09/11] gfs2: enhance log_blocks trace point to show log blocks free Bob Peterson
2020-07-24 18:33 ` [Cluster-devel] [GFS2 PATCH 10/11] gfs2: print details on transactions that aren't properly ended Bob Peterson
2020-07-24 18:33 ` [Cluster-devel] [GFS2 PATCH 11/11] gfs2: Never call gfs2_block_zero_range with an open transaction 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=20200724183304.366913-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).