From: Bob Peterson <rpeterso@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH 00/17] GFS2: Pre-pull patch posting (merge window)
Date: Mon, 13 Nov 2017 08:35:45 -0600 [thread overview]
Message-ID: <20171113143602.1319-1-rpeterso@redhat.com> (raw)
Hi,
We've got a total of 17 GFS2 patches for this merge window. The
patches are basically in three categories: (1) patches related to
broken xfstest cases, (2) patches related to improving iomap and
start using it in GFS2, and (3) general typos and clarifications.
Please note that one of the iomap patches extends beyond GFS2 and
affects other file systems, but it was publically reviewed by a
variety of file system people in the community.
1. Andreas has a patch that simply renames variable 'bsize' to 'factor'
to clarify the logic related to gfs2_block_map.
2. He also has a patch to correctly set ctime in the setflags ioctl,
which fixes broken xfstests test 277.
3. He also fixed broken xfstest 258, due to an atime initialization
problem.
4. He also fixed broken xfstest 307, in which GFS2 was not setting
ctime when setting acls.
5. He has a patch to switch general iomap code from blkno to disk
offset for a variety of file systems.
6. He has a patch to add a new IOMAP_F_DATA_INLINE flag for iomap
to indicate blocks that have data mixed with metadata.
7. I contributed a patch to make inode height info part of the
'metapath' data structure to facilitate using iomap in GFS2.
8. I have a patch to start using iomap inside GFS2 and switch GFS2's
block_map functions to use iomap under the covers.
9. I have a patch to switch GFS2's fiemap implementation from using
block_map to using iomap under the covers.
10. Andreas has a patch to implement SEEK_HOLE and SEEK_DATA via
iomap in GFS2.
11. I have a patch related to journaled data pages not being properly
synced to media when writing inodes. This was caught with xfstests.
12. I have a patch to fix another failing xfstest case in which
switching a file from ordered_write to journaled data via set_flags
caused a deadlock.
13. Andreas has a patch to fix failing xfstest case 066, which was
due to not properly syncing dirty inodes when changing extended
attributes.
14. Andreas fixed a minor typo in a comment.
15. Andreas contributed a patch to partially fix xfstest 424, which
involved GET_FLAGS and SET_FLAGS ioctl. This is also a cleanup
and simplification of the translation of flags from fs flags to
gfs2 flags.
16. He also added support for STATX_ATTR_ in statx, which fixed broken
xfstest 424.
17. He also contributed a fix for failing xfstest 093 which fixes a
recursive glock problem with gfs2_xattr_get and _set.
Regards,
Bob Peterson
---
Andreas Gruenbacher (12):
gfs2: Clarify gfs2_block_map
gfs2: Update ctime in setflags ioctl
gfs2: Support negative atimes
gfs2: Always update inode ctime in set_acl
iomap: Switch from blkno to disk offset
iomap: Add IOMAP_F_DATA_INLINE flag
gfs2: Implement SEEK_HOLE / SEEK_DATA via iomap
gfs2: Fix xattr fsync
gfs2: Fix a harmless typo
gfs2: Fix and clean up {GET,SET}FLAGS ioctl
gfs2: Add support for statx inode flags
gfs2: Allow gfs2_xattr_set to be called with the glock held
Bob Peterson (5):
GFS2: Make height info part of metapath
GFS2: Implement iomap for block_map
GFS2: Switch fiemap implementation to use iomap
GFS2: flush the log and all pages for jdata as we do for WB_SYNC_ALL
GFS2: Take inode off order_write list when setting jdata flag
--
2.13.6
next reply other threads:[~2017-11-13 14:35 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-13 14:35 Bob Peterson [this message]
2017-11-13 14:35 ` [Cluster-devel] [PATCH 01/17] gfs2: Clarify gfs2_block_map Bob Peterson
2017-11-13 14:35 ` [Cluster-devel] [PATCH 02/17] gfs2: Update ctime in setflags ioctl Bob Peterson
2017-11-13 14:35 ` [Cluster-devel] [PATCH 03/17] gfs2: Support negative atimes Bob Peterson
2017-11-13 14:35 ` [Cluster-devel] [PATCH 04/17] gfs2: Always update inode ctime in set_acl Bob Peterson
2017-11-13 14:35 ` [Cluster-devel] [PATCH 05/17] iomap: Switch from blkno to disk offset Bob Peterson
2017-11-13 14:35 ` [Cluster-devel] [PATCH 06/17] iomap: Add IOMAP_F_DATA_INLINE flag Bob Peterson
2017-11-13 14:35 ` [Cluster-devel] [PATCH 07/17] GFS2: Make height info part of metapath Bob Peterson
2017-11-13 14:35 ` [Cluster-devel] [PATCH 08/17] GFS2: Implement iomap for block_map Bob Peterson
2017-11-13 14:35 ` [Cluster-devel] [PATCH 09/17] GFS2: Switch fiemap implementation to use iomap Bob Peterson
2017-11-13 14:35 ` [Cluster-devel] [PATCH 10/17] gfs2: Implement SEEK_HOLE / SEEK_DATA via iomap Bob Peterson
2017-11-13 14:35 ` [Cluster-devel] [PATCH 11/17] GFS2: flush the log and all pages for jdata as we do for WB_SYNC_ALL Bob Peterson
2017-11-13 14:35 ` [Cluster-devel] [PATCH 12/17] GFS2: Take inode off order_write list when setting jdata flag Bob Peterson
2017-11-13 14:35 ` [Cluster-devel] [PATCH 13/17] gfs2: Fix xattr fsync Bob Peterson
2017-11-13 14:35 ` [Cluster-devel] [PATCH 14/17] gfs2: Fix a harmless typo Bob Peterson
2017-11-13 14:36 ` [Cluster-devel] [PATCH 15/17] gfs2: Fix and clean up {GET, SET}FLAGS ioctl Bob Peterson
2017-11-13 14:36 ` [Cluster-devel] [PATCH 16/17] gfs2: Add support for statx inode flags Bob Peterson
2017-11-13 14:36 ` [Cluster-devel] [PATCH 17/17] gfs2: Allow gfs2_xattr_set to be called with the glock held 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=20171113143602.1319-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).